On Thu, Mar 14, 2013 at 10:42:16AM -0700, Josh Triplett wrote: > On Thu, Mar 14, 2013 at 12:08:35AM -0400, Theodore Ts'o wrote: > > Huh. This is very, very weird. Is this a repeatable crash? > > I could reliably replicate it for that particular session, but now that > I've rebooted the host, no. Well, I can tell you that from the stack trace, it looks like when the file system was first being mounted, and the journal was being replayed (which makes sense since you snapshotted a live file system), when the journal inode was read in, it appeared to be corrupt. While trying to print an message declaring that the file system was corrupt (via ext4_error()), we somehow dereferenced a NULL pointer. I can't quite see how this could have happened; I can't understand how the journal inode would have looked corrupt in the first place, and if it was corrupt, how it could have triggered a NULL dereference. So I must be missing something.... - Ted -- To unsubscribe from this list: send the line "unsubscribe linux-ext4" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
