On Thu, Mar 14, 2013 at 12:36:09AM -0600, Russell Coker wrote: > On Thu, 14 Mar 2013, Chris Mason <chris.mason@xxxxxxxxxxxx> wrote: > > Bad key ordering is pretty rare, and it usually means memory > > corruptions. Are you reproducing this on the same machine or a > > different one? > > I've attached a kernel message log of mounting it on another system (which > incidentally has ECC RAM) running the Debian package of kernel 3.8.2. The end > result of this was a system on which the sync command blocked in D state > indefinitely and which couldn't be rebooted in any way other than a hardware > reset. Just to make sure I've got the sequence right, this is mounting the same corrupted image on a second system? The end result of that should be some messages about the bad blocks we found and then the FS forced readonly. If not, you're right there is definitely a bug there. -chris -- 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
