On Wed, Mar 12, 2014 at 11:24 AM, Josef Bacik <jbacik@xxxxxx> wrote: > On 03/12/2014 08:56 AM, Rich Freeman wrote: >> >> After a number of reboots the system became stable, presumably >> whatever race condition btrfs was hitting followed a favorable >> path. >> >> I do have a 2GB btrfs-image pre-dating my application of this >> patch that was causing the issue last week. >> > > Uhm wow that's pretty epic. I will talk to chris and figure out how > we want to deal with that and send you a patch shortly. Thanks, If you need any info from me at all beyond the capture let me know. A tiny bit more background. The system would boot normally, but panic after about 30-90 seconds (usually long enough to log into KDE, perhaps even fire up a browser/etc). In single-user mode I could mount the filesystem read-only without issue. If I mounted it read-write (in recovery mode or normally) I'd get the panic after about 30-60 seconds. On one occasion it seemed stable, but panicked when I unmounted it. I have to say that I'm impressed that it recovers at all. I'd rather have the file system not write anything if it isn't sure it can't write it correctly, and that seems to be the effect here. Just about all the issues I've run into with btrfs have tended to be lockup/etc type issues, and not silent corruption. Rich -- 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
