XFS dirty after sync/reboot?
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
While triaging a bug filed in Ubuntu involving odd reboot failures, it appears that XFS leaves the filesystem in a corrupt state that requires journal playback to fix after a sync or reboot. Grub2 doesn't seem to understand the journal, leading to all kinds of confusion after the reboot.
Shouldn't a full sync or remount to r/o flush the journal transactions and leave the fs fully clean?
Original bug report: https://launchpad.net/bugs/1103187
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.17 (MingW32)
Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/
iQEcBAEBAgAGBQJRAs/XAAoJEJrBOlT6nu75gogH/1Q+ej+QBqmzQpPLB9jFbiFs EqDLyV0tJg0R5zF3PRVFC7Qh3IWqDkt0H2aXWnhPVItDjIRIicV51vgtCpxkgxHC HCwheiGwVwXj0GK/Z5OfCyxEupZI9ThLu5rc9hRypMzFMKULW5WRazo5oXZpvZ3E XvNxG3Ey0QbiFjzaClbpWTiTV+kjoeHCnkNQ/cYMLqdKXgkMWuDgCj1q8NkT6AZL z9cJgssxYRdrzAQgjZ9YxUxVpuAIuQQUJxpXZFT7bd7jpsJ109q3i7BQ+j8aZxHW 8Xy2zTWGMZsfxLUHIUvwOXORYz/GXfVkjHOJC6SnqUErInOvMIDPsutIgyFw/LM= =i0Bt
-----END PGP SIGNATURE-----
Hey Philip,
Quoted 11 lines · Phillip Susi
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1While triaging a bug filed in Ubuntu involving odd reboot failures, it appears that XFS leaves the filesystem in a corrupt state that requires journal playback to fix after a sync or reboot. Grub2 doesn't seem to understand the journal, leading to all kinds of confusion after the reboot.
Shouldn't a full sync or remount to r/o flush the journal transactions and leave the fs fully clean?
It should. We have a bug in xfs in that area.
Quoted 1 line
Original bug report: https://launchpad.net/bugs/1103187
Try this patch which was recently proposed for 3.5-3.7 stable trees:
http://oss.sgi.com/archives/xfs/2012-12/msg00324.html
Regards,
Ben