Hey, When I try to mount my Btrfs filesystem it fails and this shows up on dmesg: device fsid 97727502-a678-4ed1-a96c-409b852d76bf devid 1 transid 135714 /dev/sda4 btrfs: enabling auto recoveryparent transid verify failed on 216925220864 wanted 135714 found 135713 parent transid verify failed on 216925220864 wanted 135714 found 135713 parent transid verify failed on 216925220864 wanted 135714 found 135713 btrfs: open_ctree failed Using the latest btrfs-progs, btrfsck and btrfs-debug-tree gives this: parent transid verify failed on 216925220864 wanted 135714 found 135713 parent transid verify failed on 216925220864 wanted 135714 found 135713 parent transid verify failed on 216925220864 wanted 135714 found 135713 parent transid verify failed on 216925220864 wanted 135714 found 135713 Ignoring transid failure btrfsck: root-tree.c:46: btrfs_find_last_root: Assertion `!(path->slots[0] == 0)'' failed. I also couldn''t find anything valid using btrfs-select-super. This is find-root''s output: http://pastebin.com/KycgzhaP Is there anything else I can try? I''m using kernel 3.2 on Ubuntu 12.04. Thanks in advance, Yo''av -- To unsubscribe from this list: send the line "unsubscribe linux-btrfs" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
On Thu, May 03, 2012 at 03:18:01PM +0000, Yo''av Moshe wrote:> Hey, > > When I try to mount my Btrfs filesystem it fails and this shows up on dmesg: > > device fsid 97727502-a678-4ed1-a96c-409b852d76bf devid 1 transid > 135714 /dev/sda4 > btrfs: enabling auto recoveryparent transid verify failed on > 216925220864 wanted 135714 found 135713 > parent transid verify failed on 216925220864 wanted 135714 found 135713 > parent transid verify failed on 216925220864 wanted 135714 found 135713 > btrfs: open_ctree failed > > Using the latest btrfs-progs, btrfsck and btrfs-debug-tree gives this: > > parent transid verify failed on 216925220864 wanted 135714 found 135713 > parent transid verify failed on 216925220864 wanted 135714 found 135713 > parent transid verify failed on 216925220864 wanted 135714 found 135713 > parent transid verify failed on 216925220864 wanted 135714 found 135713 > Ignoring transid failure > btrfsck: root-tree.c:46: btrfs_find_last_root: Assertion > `!(path->slots[0] == 0)'' failed. > > I also couldn''t find anything valid using btrfs-select-super. > > This is find-root''s output: > http://pastebin.com/KycgzhaP > > Is there anything else I can try? > > I''m using kernel 3.2 on Ubuntu 12.04.In approximate order: * Try a 3.3 or 3.4-rc5 kernel. I don''t think those will do anything to fix this particular issue, but it''s worth a try. * You have the last-but-one generation listed by find-root: Well block 216926195712 seems great, but generation doesn''t match, have=135713, want=135714 so you can use the restore tool[1] with that block number (and -t) to copy off any data that you need that isn''t backed up. * There''s btrfsck --repair, which may do something to fix it in-place, but may not (or may damage your filesystem more) * And, of course, there''s your backups that you can restore from. Hugo. [1] http://btrfs.ipv5.de/index.php?title=Restore -- === Hugo Mills: hugo@... carfax.org.uk | darksatanic.net | lug.org.uk == PGP key: 515C238D from wwwkeys.eu.pgp.net or http://www.carfax.org.uk --- emacs: Eats Memory and Crashes. ---
On Thu, May 3, 2012 at 10:31 PM, Hugo Mills <hugo@carfax.org.uk> wrote:> On Thu, May 03, 2012 at 03:18:01PM +0000, Yo''av Moshe wrote:>> Is there anything else I can try? >> >> I''m using kernel 3.2 on Ubuntu 12.04. > > In approximate order: > > * Try a 3.3 or 3.4-rc5 kernel. I don''t think those will do anything > to fix this particular issue, but it''s worth a try. > > * You have the last-but-one generation listed by find-root: > > Well block 216926195712 seems great, but generation doesn''t match, have=135713, want=135714 > > so you can use the restore tool[1] with that block number (and -t) > to copy off any data that you need that isn''t backed up.Is btrfs-zero-log still relevant? I imagine losing several last transactions is MUCH more convinient than having to recreate the enitre fs (even if restore managed to salvage everything). And what about mont -o ro,recover? -- Fajar -- To unsubscribe from this list: send the line "unsubscribe linux-btrfs" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
On Fri, May 04, 2012 at 10:43:16AM +0700, Fajar A. Nugraha wrote:> Is btrfs-zero-log still relevant? I imagine losing several last > transactions is MUCH more convinient than having to recreate the > enitre fs (even if restore managed to salvage everything).IMHO it is, a few days ago this helped one user to mount his filesystem (other usual steps to recover from unmountable filesystem did not help).> And what about mont -o ro,recover?I saw in the logs that the -o recovery must have been used, quoting from the mail:> device fsid 97727502-a678-4ed1-a96c-409b852d76bf devid 1 transid > 135714 /dev/sda4 > btrfs: enabling auto recoveryparent transid verify failed on 216925220864 wanted 135714 found 135713^^^^^^^^^^^^^^^^^^^^^^> parent transid verify failed on 216925220864 wanted 135714 found 135713 > parent transid verify failed on 216925220864 wanted 135714 found 135713 > btrfs: open_ctree failedand the RO mount does not make any difference here. david -- To unsubscribe from this list: send the line "unsubscribe linux-btrfs" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
Hey, Thanks everybody. Upgrading the kernel really did not help, and btrfsck --repair also, so I ended up using btrfs-restore. Some files are gone but I should have them backed up somewhere :-) Thanks again. I''ve had this FS broken for almost 2 years now. Yo''av 2012/5/4 David Sterba <dave@jikos.cz>> > On Fri, May 04, 2012 at 10:43:16AM +0700, Fajar A. Nugraha wrote: > > Is btrfs-zero-log still relevant? I imagine losing several last > > transactions is MUCH more convinient than having to recreate the > > enitre fs (even if restore managed to salvage everything). > > IMHO it is, a few days ago this helped one user to mount his filesystem > (other > usual steps to recover from unmountable filesystem did not help). > > > And what about mont -o ro,recover? > > I saw in the logs that the -o recovery must have been used, quoting from > the > mail: > > > device fsid 97727502-a678-4ed1-a96c-409b852d76bf devid 1 transid > > 135714 /dev/sda4 > > btrfs: enabling auto recoveryparent transid verify failed on > > 216925220864 wanted 135714 found 135713 > ^^^^^^^^^^^^^^^^^^^^^^ > > parent transid verify failed on 216925220864 wanted 135714 found 135713 > > parent transid verify failed on 216925220864 wanted 135714 found 135713 > > btrfs: open_ctree failed > > and the RO mount does not make any difference here. > > > david-- Yo''av Moshe -- To unsubscribe from this list: send the line "unsubscribe linux-btrfs" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html