On 5/16/17 5:06 AM, Jan Beulich wrote: >> I'm not sure we've made much progress on the root cause of whatever set >> those extra flags*, > Indeed, and that's the primary aspect that worries me, since with > working on the hypervisor or kernel it is going to be unavoidable for > a crash to happen now and then. While I realize chances are low to > find out any useful information for the two past cases of corruption, > do you have any advice on how to collect / preserve necessary > information on a sooner or later to be expected next instance? Isn't > the most likely explanation that the log replay upon next mount has > gone wrong (or the data in the log itself was bogus)? About all I can suggest is to get an xfs_metadump as soon as any new problem shows up, if it does. Your first report seems to indicate that a 4.11 kernel crashed, and the resulting dirty log was replayed by a 3.12-era distro kernel. Is that the correct sequence of events? -Eric -- To unsubscribe from this list: send the line "unsubscribe linux-xfs" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
