From: Karsten Hopp <karsten@redhat.com>
To: Theodore Tso <tytso@mit.edu>, linux-ext4@vger.kernel.org
Subject: Re: Patch to support LUKS UUIDs in libblkid
Date: Mon, 23 Jul 2007 17:00:02 +0200 [thread overview]
Message-ID: <46A4C272.3040907@redhat.com> (raw)
In-Reply-To: <46964694.7000707@redhat.com>
Theodore Tso schrieb:
> Thanks, I've applied the blkid LUKS patch to the e2fsprogs SCM (modulo
> a minor whitespace breakage which I fixed up).
>
I've encountered a problem with this patch, consider the following
setup:
in /etc/fstab:
UUID=<some LUKS uuid> / ext3 defaults 0 0
During bootup the init scripts run 'fsck -A', fsck reads in /etc/fstab and
converts the LUKS-uuid to a device name. It then uses this devicename to
populate filesys_info and sets the type to ext3 (from fstab). It then tries to check
the underlying device instead of the /dev/mapper/ LUKS device.
I'm not sure how to work around this, adding crypt_luks to ignored_types won't work
because fsck thinks the device has an ext3 FS.
Is create_fs_device() the right place to add a check if this is a LUKS device or would it be better
to do that in parse_fstab_line() around the blkid_get_devname() call ?
Karsten
--
Karsten Hopp | Mail: karsten@redhat.de
Red Hat Deutschland | Tel: +49-711-96437-0
Hauptstaetterstr.58 | Fax: +49-711-613590
D-70178 Stuttgart | http://www.redhat.de
next prev parent reply other threads:[~2007-07-23 15:00 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-06-05 11:23 Patch to support LUKS UUIDs in libblkid Karsten Hopp
2007-06-05 14:20 ` Eric Sandeen
2007-06-05 23:17 ` Andreas Dilger
2007-06-08 15:36 ` Theodore Tso
2007-06-11 11:51 ` Karsten Hopp
2007-06-12 23:40 ` Theodore Tso
2007-06-13 11:00 ` Karsten Hopp
2007-06-21 17:56 ` Theodore Tso
2007-07-03 9:19 ` Karsten Hopp
2007-07-03 15:57 ` Eric Sandeen
[not found] ` <46964694.7000707@redhat.com>
2007-07-23 15:00 ` Karsten Hopp [this message]
2007-07-23 16:19 ` Theodore Tso
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=46A4C272.3040907@redhat.com \
--to=karsten@redhat.com \
--cc=linux-ext4@vger.kernel.org \
--cc=tytso@mit.edu \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.