From: Ferry Toth <fntoth@gmail.com>
To: Andrei Borzenkov <arvidjaar@gmail.com>
Cc: Qu Wenruo <wqu@suse.com>, Qu Wenruo <quwenruo.btrfs@gmx.com>,
Tyler Richmond <t.d.richmond@gmail.com>,
Btrfs BTRFS <linux-btrfs@vger.kernel.org>
Subject: Re: Fwd: Read time tree block corruption detected
Date: Mon, 16 Nov 2020 11:57:20 +0100 [thread overview]
Message-ID: <b0a07c20-974d-0cbd-7884-bee3b43bda91@gmail.com> (raw)
In-Reply-To: <CAA91j0XLWcHsj4K4QfMOfQ01a43OJxPO-P246Y-wZ9c=uFP=Ow@mail.gmail.com>
Hi,
Op 16-11-2020 om 11:52 schreef Andrei Borzenkov:
> On Mon, Nov 16, 2020 at 1:44 PM Ferry Toth <fntoth@gmail.com> wrote:
>> - Built btrfs-progs v5.9 from
>> git://git.kernel.org/pub/scm/linux/kernel/git/kdave/btrfs-progs.git and
>> booting Kubuntu 20.10 from USB stick then running btrfs-progs v5.9 fixes
>> it with below log.
>>
> What do you mean "fixes"? "btrfs check" is read-only by default so
> your invocation could not fix anything. Was it the only command you
> invoked?
Yeah, immediately after that command I ran
sudo ./btrfs check --repair /dev/sda2
to really repair, and then I could clean up:
rm -rf /usr/share/dog
>> - Thanks Qu for the help!
>>
>> Ferry
>>
>> log
>>
>> ---
>>
>> kubuntu@kubuntu:~$ sudo ./btrfs check /dev/sda2
>> Opening filesystem to check...
>> Checking filesystem on /dev/sda2
>> UUID: 27155120-9ef8-47fb-b248-eaac2b7c8375
>> [1/7] checking root items
>> [2/7] checking extents
>> [3/7] checking free space cache
>> [4/7] checking fs roots
>> root 294 inode 915975 errors 100000, invalid inode generation or transid
>> root 294 inode 915976 errors 100000, invalid inode generation or transid
>> root 294 inode 915977 errors 100000, invalid inode generation or transid
>> root 294 inode 915978 errors 100000, invalid inode generation or transid
>> root 294 inode 915979 errors 100000, invalid inode generation or transid
>> root 294 inode 915980 errors 100000, invalid inode generation or transid
>> root 294 inode 915982 errors 100000, invalid inode generation or transid
>> root 294 inode 915984 errors 100000, invalid inode generation or transid
>> root 294 inode 915985 errors 100000, invalid inode generation or transid
>> root 294 inode 915987 errors 100000, invalid inode generation or transid
>> root 294 inode 1962496 errors 100000, invalid inode generation or transid
>> root 294 inode 1962499 errors 100000, invalid inode generation or transid
>> root 294 inode 1962500 errors 100000, invalid inode generation or transid
>> root 294 inode 1962501 errors 100000, invalid inode generation or transid
>> root 294 inode 1962502 errors 100000, invalid inode generation or transid
>> root 294 inode 1962503 errors 100000, invalid inode generation or transid
>> root 294 inode 1962504 errors 100000, invalid inode generation or transid
>> root 294 inode 1962505 errors 100000, invalid inode generation or transid
>> root 294 inode 1962506 errors 100000, invalid inode generation or transid
>> root 294 inode 1962507 errors 100000, invalid inode generation or transid
>> root 294 inode 1962508 errors 100000, invalid inode generation or transid
>> root 294 inode 1962509 errors 100000, invalid inode generation or transid
>> root 294 inode 1962510 errors 100000, invalid inode generation or transid
>> root 294 inode 1962511 errors 100000, invalid inode generation or transid
>> root 294 inode 1962512 errors 100000, invalid inode generation or transid
>> root 294 inode 1962513 errors 100000, invalid inode generation or transid
>> root 294 inode 1962514 errors 100000, invalid inode generation or transid
>> root 294 inode 1962515 errors 100000, invalid inode generation or transid
>> root 294 inode 1962516 errors 100000, invalid inode generation or transid
>> root 294 inode 1962517 errors 100000, invalid inode generation or transid
>> root 294 inode 1962518 errors 100000, invalid inode generation or transid
>> root 294 inode 1962519 errors 100000, invalid inode generation or transid
>> root 294 inode 1962520 errors 100000, invalid inode generation or transid
>> root 294 inode 1962521 errors 100000, invalid inode generation or transid
>> root 294 inode 1962522 errors 100000, invalid inode generation or transid
>> root 294 inode 1962523 errors 100000, invalid inode generation or transid
>> root 294 inode 1962524 errors 100000, invalid inode generation or transid
>> root 294 inode 1962525 errors 100000, invalid inode generation or transid
>> root 294 inode 1962526 errors 100000, invalid inode generation or transid
>> root 294 inode 1962527 errors 100000, invalid inode generation or transid
>> root 294 inode 1962528 errors 100000, invalid inode generation or transid
>> root 294 inode 1962529 errors 100000, invalid inode generation or transid
>> root 294 inode 1962530 errors 100000, invalid inode generation or transid
>> root 294 inode 1962531 errors 100000, invalid inode generation or transid
>> root 294 inode 1962532 errors 100000, invalid inode generation or transid
>> root 294 inode 1962533 errors 100000, invalid inode generation or transid
>> root 294 inode 1962534 errors 100000, invalid inode generation or transid
>> root 294 inode 1962535 errors 100000, invalid inode generation or transid
>> root 294 inode 1962536 errors 100000, invalid inode generation or transid
>> root 294 inode 1962537 errors 100000, invalid inode generation or transid
>> root 294 inode 1962538 errors 100000, invalid inode generation or transid
>> root 294 inode 1962539 errors 100000, invalid inode generation or transid
>> root 294 inode 1962540 errors 100000, invalid inode generation or transid
>> root 294 inode 1962541 errors 100000, invalid inode generation or transid
>> root 294 inode 1962542 errors 100000, invalid inode generation or transid
>> root 294 inode 1962543 errors 100000, invalid inode generation or transid
>> root 294 inode 1962544 errors 100000, invalid inode generation or transid
>> root 294 inode 1962545 errors 100000, invalid inode generation or transid
>> root 294 inode 1962546 errors 100000, invalid inode generation or transid
>> root 294 inode 1962547 errors 100000, invalid inode generation or transid
>> root 294 inode 1962548 errors 100000, invalid inode generation or transid
>> root 294 inode 1962549 errors 100000, invalid inode generation or transid
>> root 294 inode 1962550 errors 100000, invalid inode generation or transid
>> root 294 inode 1962551 errors 100000, invalid inode generation or transid
>> root 294 inode 1962552 errors 100000, invalid inode generation or transid
>> root 294 inode 1962553 errors 100000, invalid inode generation or transid
>> root 294 inode 1962554 errors 100000, invalid inode generation or transid
>> root 294 inode 1962555 errors 100000, invalid inode generation or transid
>> root 294 inode 1962556 errors 100000, invalid inode generation or transid
>> root 294 inode 1962557 errors 100000, invalid inode generation or transid
>> root 294 inode 1962558 errors 100000, invalid inode generation or transid
>> root 294 inode 1962559 errors 100000, invalid inode generation or transid
>> root 294 inode 1962560 errors 100000, invalid inode generation or transid
>> root 294 inode 1962561 errors 100000, invalid inode generation or transid
>> root 294 inode 1962562 errors 100000, invalid inode generation or transid
>> root 294 inode 1962563 errors 100000, invalid inode generation or transid
>> root 294 inode 1962564 errors 100000, invalid inode generation or transid
>> root 294 inode 1962565 errors 100000, invalid inode generation or transid
>> root 294 inode 1962566 errors 100000, invalid inode generation or transid
>> root 294 inode 1962567 errors 100000, invalid inode generation or transid
>> root 294 inode 1962568 errors 100000, invalid inode generation or transid
>> root 294 inode 1962569 errors 100000, invalid inode generation or transid
>> root 294 inode 1962570 errors 100000, invalid inode generation or transid
>> root 294 inode 1962571 errors 100000, invalid inode generation or transid
>> root 294 inode 1962572 errors 100000, invalid inode generation or transid
>> root 294 inode 1962573 errors 100000, invalid inode generation or transid
>> root 294 inode 1962574 errors 100000, invalid inode generation or transid
>> root 294 inode 1962575 errors 100000, invalid inode generation or transid
>> root 294 inode 1962576 errors 100000, invalid inode generation or transid
>> root 294 inode 1962577 errors 100000, invalid inode generation or transid
>> root 294 inode 1962578 errors 100000, invalid inode generation or transid
>> root 294 inode 1962579 errors 100000, invalid inode generation or transid
>> root 294 inode 1962580 errors 100000, invalid inode generation or transid
>> root 294 inode 1962581 errors 100000, invalid inode generation or transid
>> root 294 inode 1962582 errors 100000, invalid inode generation or transid
>> root 294 inode 1962583 errors 100000, invalid inode generation or transid
>> root 294 inode 1962584 errors 100000, invalid inode generation or transid
>> root 294 inode 1962585 errors 100000, invalid inode generation or transid
>> root 294 inode 1962586 errors 100000, invalid inode generation or transid
>> ERROR: errors found in fs roots
>> found 444725678080 bytes used, error(s) found
>> total csum bytes: 272354940
>> total tree bytes: 1862316032
>> total fs tree bytes: 1250484224
>> total extent tree bytes: 277397504
>> btree space waste bytes: 401028956
>> file data blocks allocated: 16021691621376
>> referenced 394733535232
>>
>>
next prev parent reply other threads:[~2020-11-16 12:27 UTC|newest]
Thread overview: 56+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <CAJheHN0FUe-ijMco1ZOc6iKF2zbPocOw+iiVNeTT1r-JuXOJww@mail.gmail.com>
2020-05-06 21:54 ` Fwd: Read time tree block corruption detected Tyler Richmond
2020-05-06 23:55 ` Chris Murphy
2020-05-07 0:51 ` Tyler Richmond
2020-05-07 1:06 ` Chris Murphy
2020-05-07 1:13 ` Fwd: " Qu Wenruo
2020-05-07 1:30 ` Tyler Richmond
2020-05-07 5:43 ` Tyler Richmond
2020-05-07 5:52 ` Qu Wenruo
2020-05-07 15:52 ` Tyler Richmond
2020-05-08 0:11 ` Qu Wenruo
2020-05-08 4:23 ` Tyler Richmond
2020-05-08 5:07 ` Qu Wenruo
2020-05-08 5:12 ` Tyler Richmond
2020-05-08 5:47 ` Qu Wenruo
2020-05-08 13:52 ` Tyler Richmond
2020-08-18 3:36 ` Tyler Richmond
[not found] ` <CAJheHN3qwDAGY=z14zfO4LBrxNJZZ_rvAMsWLwe-k+4+t3zLog@mail.gmail.com>
2020-08-18 6:07 ` Qu Wenruo
2020-08-18 12:18 ` Tyler Richmond
2020-08-23 1:15 ` Tyler Richmond
2020-08-23 1:51 ` Qu Wenruo
2020-08-23 2:31 ` Qu Wenruo
2020-08-23 2:49 ` Tyler Richmond
2020-08-23 4:28 ` Qu Wenruo
2020-08-24 2:47 ` Tyler Richmond
2020-08-24 8:26 ` Qu Wenruo
2020-08-25 5:25 ` Tyler Richmond
2020-08-25 6:37 ` Qu Wenruo
2020-08-25 13:30 ` Tyler Richmond
2020-08-25 13:38 ` Qu Wenruo
2020-08-25 13:43 ` Tyler Richmond
2020-11-05 7:01 ` Tyler Richmond
2020-11-05 7:19 ` Qu Wenruo
2020-11-05 20:08 ` Ferry Toth
2020-11-05 23:00 ` Qu Wenruo
2020-11-05 23:12 ` Ferry Toth
2020-11-05 23:32 ` Qu Wenruo
2020-11-05 23:37 ` Ferry Toth
2020-11-05 23:40 ` Qu Wenruo
2020-11-06 10:09 ` Ferry Toth
2020-11-06 10:24 ` Qu Wenruo
2020-11-06 10:27 ` Qu Wenruo
2020-11-06 10:32 ` Ferry Toth
2020-11-06 10:30 ` Ferry Toth
2020-11-06 10:32 ` Qu Wenruo
2020-11-07 11:18 ` Ferry Toth
2020-11-07 11:35 ` Qu Wenruo
2020-11-07 13:19 ` Ferry Toth
2020-11-07 13:28 ` Qu Wenruo
2020-11-07 19:50 ` Ferry Toth
2020-11-07 19:50 ` Ferry Toth
2020-11-16 10:41 ` Ferry Toth
2020-11-16 10:52 ` Andrei Borzenkov
2020-11-16 10:57 ` Ferry Toth [this message]
2020-11-16 16:35 ` Tyler Richmond
2020-11-06 11:28 ` Ferry Toth
2020-08-23 2:32 ` Tyler Richmond
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=b0a07c20-974d-0cbd-7884-bee3b43bda91@gmail.com \
--to=fntoth@gmail.com \
--cc=arvidjaar@gmail.com \
--cc=linux-btrfs@vger.kernel.org \
--cc=quwenruo.btrfs@gmx.com \
--cc=t.d.richmond@gmail.com \
--cc=wqu@suse.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).