On Thu, Sep 23, 2010 at 08:24, Francis Galiegue <fgaliegue@xxxxxxxxx> wrote: [...] > > For this particular filesystem, which contains qemu-kvm disk images in > raw mode with caching mode set to "writeback", the symptoms is that: > > * in 2.6.34 and lower, I could mount the filesystem, with the "parent > transid verify failed" message appearing once; > * with 2.6.35+ and upper, however, not anymore: I mount it and the > same "parent transid very failed" message now floods dmesg, and I > cannot kill -9 any program trying to access that filesystem. > [...] Another thing: as I can afford to recreate the hosed filesystem if need be, I'm also ready to try any offline (of course) repairing btrfsck on this filesystem and see if I can mount it again safely. Any btrfs-progs tree that I might try out? I have the possibility to boot from a USB key with a sufficiently recent kernel and test that, and attempt to mount the fs again... -- Francis Galiegue, fgaliegue@xxxxxxxxx "It seems obvious [...] that at least some 'business intelligence' tools invest so much intelligence on the business side that they have nothing left for generating SQL queries" (StÃphane Faroult, in "The Art of SQL", ISBN 0-596-00894-5) -- 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
