From: Ian Kelling <iank@fsf.org>
To: linux-btrfs@vger.kernel.org
Subject: Re: I got a write time tree block corruption detected
Date: Thu, 07 Oct 2021 16:54:36 -0400 [thread overview]
Message-ID: <871r4wr1t3.fsf@fsf.org> (raw)
In-Reply-To: <87ily8y9c8.fsf@fsf.org>
[-- Attachment #1: Type: text/plain, Size: 1654 bytes --]
For this log line,
[Thu Oct 7 13:04:41 2021] BTRFS critical (device dm-3): corrupt leaf: root=5 block=5558935797760 slot=0 ino=161138910, invalid nlink: has 2 expect no more than 1 for dir
I see a previous report on the list and someone requested output of a command (
https://lore.kernel.org/linux-btrfs/fb556cb2-4444-005f-4a94-6346f2a641ac@gmx.com/ )
btrfs ins dump-tree -b 5558935797760 /dev/dm-3
The output is rather long, I've attached it, but here is the head and tail
also in case that is enough:
btrfs-progs v5.10.1
leaf 5558935797760 items 244 free space 2131 generation 129446 owner EXTENT_TREE
leaf 5558935797760 flags 0x1(WRITTEN) backref revision 1
fs uuid cdbab81e-20ec-49e6-904c-649f6096b112
chunk uuid 41516bf2-a2b3-4793-bb1c-bbcb8a7cca40
item 0 key (15927669194752 METADATA_ITEM 0) itemoff 16250 itemsize 33
refs 1 gen 129210 flags TREE_BLOCK
tree block skinny level 0
tree block backref root EXTENT_TREE
item 1 key (15927669211136 METADATA_ITEM 0) itemoff 16217 itemsize 33
refs 1 gen 129216 flags TREE_BLOCK
tree block skinny level 0
tree block backref root FS_TREE
...
item 242 key (15927673700352 METADATA_ITEM 0) itemoff 8264 itemsize 33
refs 1 gen 129225 flags TREE_BLOCK
tree block skinny level 0
tree block backref root FS_TREE
item 243 key (15927673716736 METADATA_ITEM 0) itemoff 8231 itemsize 33
refs 1 gen 129239 flags TREE_BLOCK
tree block skinny level 0
tree block backref root EXTENT_TREE
[-- Attachment #2: btrfs_ins_dump-tree.tgz --]
[-- Type: application/x-gtar-compressed, Size: 4037 bytes --]
[-- Attachment #3: Type: text/plain, Size: 168 bytes --]
--
Ian Kelling | Senior Systems Administrator, Free Software Foundation
GPG Key: B125 F60B 7B28 7FF6 A2B7 DF8F 170A F0E2 9542 95DF
https://fsf.org | https://gnu.org
next prev parent reply other threads:[~2021-10-07 20:57 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-10-07 18:32 I got a write time tree block corruption detected Ian Kelling
2021-10-07 20:54 ` Ian Kelling [this message]
2021-10-10 14:14 ` Ian Kelling
2021-10-10 18:00 ` Zygo Blaxell
2021-10-10 20:52 ` Ian Kelling
2021-10-10 23:57 ` Qu Wenruo
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=871r4wr1t3.fsf@fsf.org \
--to=iank@fsf.org \
--cc=linux-btrfs@vger.kernel.org \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.