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@xxxxxxxx> > > 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@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
