All of lore.kernel.org
 help / color / mirror / Atom feed
* tree-checker read time error, unable to mount
       [not found] <CAPbOkdp781Ydnj0VYSw1z3SB52H-7JQ98_YhEMZdn5jb4wockg@mail.gmail.com>
@ 2021-04-12 19:43 ` Henrik Nordström
  0 siblings, 0 replies; only message in thread
From: Henrik Nordström @ 2021-04-12 19:43 UTC (permalink / raw)
  To: linux-btrfs

We have an btrfs filesystem which have crashed and fails to mount. The
filesystem is on an extrenal SSD and it is quite possible it got
disconnected badly or had an unclean shutdown due to suspend issues.

[  447.321770] BTRFS critical (device sdc3): corrupt leaf: root=256
block=2036170752 slot=1 ino=806641, invalid inode transid: has 77966
expect [0, 77889]
[  447.321775
] BTRFS error (device sdc3): block=2036170752 read time tree block
corruption detected
[  447.321797] BTRFS error (device sdc3): failed to read block groups: -5
[  447.322328] BTRFS error (device sdc3): open_ctree failed

Host used for analyzing the disk (Fedora 33):

[root@localhost ~]# uname -r
5.11.7-200.fc33.x86_64
[root@localhost ~]# rpm -q btrfs-progs
btrfs-progs-5.10-1.fc33.x86_64

Mounting read-only also fails with the same error.

Not 100% sure which kernel was used to write to the disk when it
failed, but it's fairly recent, Fedora 34 beta. The OS that was used
is on the disk.

Data is not critical, but there is some files we like to recover if possible.

btrfs-image also fails with similar error

[root@localhost henrik_n]# btrfs-image /dev/sdc3 fedora34-beta.btrfsimage
parent transid verify failed on 2036170752 wanted 63722 found 77966
parent transid verify failed on 2036170752 wanted 63722 found 77966
Ignoring transid failure
leaf parent key incorrect 2036170752
ERROR: failed to read block groups: Operation not permitted
ERROR: open ctree failed
ERROR: create failed: -5

No difference with the -w option.

btrfs-restore do find some roots

[root@localhost henrik_n]# btrfs restore -l /dev/sdc3
 tree key (EXTENT_TREE ROOT_ITEM 0) 2056372224 level 2
 tree key (DEV_TREE ROOT_ITEM 0) 1974648832 level 0
 tree key (FS_TREE ROOT_ITEM 0) 5275648 level 0
 tree key (CSUM_TREE ROOT_ITEM 0) 2044133376 level 2
 tree key (UUID_TREE ROOT_ITEM 0) 1096368128 level 0
 tree key (256 ROOT_ITEM 0) 2043953152 level 2
 tree key (257 ROOT_ITEM 0) 2012250112 level 2
 tree key (262 ROOT_ITEM 0) 1637449728 level 0
 tree key (DATA_RELOC_TREE ROOT_ITEM 0) 5390336 level 0

btrfs-restore is quite upset as well, and only finds a handful files.

Regards

Henrik

^ permalink raw reply	[flat|nested] only message in thread

only message in thread, other threads:[~2021-04-12 19:44 UTC | newest]

Thread overview: (only message) (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
     [not found] <CAPbOkdp781Ydnj0VYSw1z3SB52H-7JQ98_YhEMZdn5jb4wockg@mail.gmail.com>
2021-04-12 19:43 ` tree-checker read time error, unable to mount Henrik Nordström

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.