On Mon, Jul 23, 2007 at 05:00:02PM +0200, Karsten Hopp wrote:
>
> I've encountered a problem with this patch, consider the following
> setup:
>
> in /etc/fstab:
> UUID=<some LUKS uuid> / ext3 defaults 0 0
Well, the problem is that what you should be putting in /etc/fstab is:
UUID=<uuid of the ext3 filesystem> / ext3 defaults 0 0
If you put "UUID=<some LUKS uuid>", then of course you will get the
underlying device; that's what you asked for --- what device has the
UUID set to <some LUKS uuid> --- and the computer gave you what you
asked for, which is what not what you wanted. :-)
If you put the UUID of the ext3 filesystem, then the blkid library
will search through the /dev/mapper devices and find the correct
/dev/mapper device for the underlying filesystem, which is as it should be.
This of course assumes that someone has correctly activated the LUKS
filesystem (and presumably passed LUKS the correct crypto information)
so that it appears as one of the /dev/mapper filesystems. If that is
why you put the UUID of LUKS partition in /etc/fstab, then we have a
fundamental conflict of what /etc/fstab is for. /etc/fstab's job is
to identify the actual devices for mounting a filesystem.
- Ted
-
To unsubscribe from this list: send the line "unsubscribe linux-ext4" in
the body of a message to [EMAIL PROTECTED]
More majordomo info at http://vger.kernel.org/majordomo-info.html
