On Thu, Sep 23, 2010 at 08:24, Francis Galiegue <fgaliegue@xxxxxxxxx> wrote: > Hello list, > > I've been using btrfs for nearly 6 months now, on three machines, with > no problems but for _one_ filesystem on one machine. The problem is > the message in $subject. > > 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. > [...] > > I just fear that I get [for my rootfs] into the situation of the hosed filesystem > which I cannot mount anymore... > And I just did. Dang. Fortunately I have the sysreccd with which I _can_ mount the filesystem! Phew. -- 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
