On 2012-07-16, at 4:00, Kevin Shanahan <kmshanah@xxxxxxxxxxxxxx> wrote: > On Sun, Jul 15, 2012 at 10:32:01PM -0600, Andreas Dilger wrote: >> >> >> Because LVM changed the block device numbers after the reboot, and >> the device number used previously for the external journal was >> different. >> >> The lookup of the journal by UUID (instead of relying on the "device >> hint" in the superblock) _should_ be handled by mount, but I don't >> recall if we ever got a mount.ext4 to handle this or not. It would >> also be possible for the "fast e2fsck" check to verify the journal >> UUID before mounting the filesystem, but again I'm not sure if this >> is done yet, and I can't check right now. > > Ok, thanks. For now I can ask LVM to make the major/minor number > persistent. > > Assuming it's not already done, do you think adding the UUID lookup > would be a reasonable project for a newbie or is it likely to be a bit > complicated? It should be fairly easy. During e2fsck checking of the superblock, it should check if there is an external journal, and then call into libblkid to find the journal UUID and verify the block device matches the value stored in the superblock. > I'm assuming support is not there, at least for the versions in Arch: > > $ pacman -Q e2fsprogs util-linux > e2fsprogs 1.42.4-1 > util-linux 2.21.2-5 This is the latest version of e2fsprogs. Cheers, Andreas-- 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
