From: Milan Broz <mbroz@redhat.com>
To: Scott Castaline <skotchman@gmail.com>
Cc: dm-crypt <dm-crypt@saout.de>
Subject: Re: [dm-crypt] Need some suggestions on large drives
Date: Sat, 06 Mar 2010 20:25:36 +0100 [thread overview]
Message-ID: <4B92AC30.5030304@redhat.com> (raw)
In-Reply-To: <4B9294CC.10501@gmail.com>
On 03/06/2010 06:45 PM, Scott Castaline wrote:
> First, does anyone know how Fedora 12's installer installs LUKS with
> LVM2? Do they do LUKS over LVM2 or LVM2 over LUKS?
You can (manually) configure both modes during partitioning,
the "encrypt whole system" checkbox will create partition, LUKS on it,
and over it LVM2 with root + swap LV.
Anaconda (Fedora installer) developers decided to use aes-xts-plain
with 512 bits key (IOW AES256 in XTS mode).
> Finally, as mentioned in the second paragraph, I have /var as seperate
> LV which is within an encrypted VG. The LV is not additionally
> encrypted, I had to expand the LV using free space from the 1st VG. I
> did it through the GUI for LVM2.
Not sure what's GUI - if it is system-config-lvm, it doesn't suport LUKS yet,
so you must be very careful. (and there were nasty bugs in this GUI, should
be fixed in recent version though).
But because LUKS have no underlying device size stored in header,
simply reactivate will reload the proper device size.
(or use cryptsetup resize command for online change).
...
> execute "e2fsck -VCa mapped-device", but I wasn't able to unmount the LV.
then you maybe need to run it from recovery or LiveCD.
(online resize LV is not problem, online resize FS on it - depends on configuration,
ext3 should allow online extension)
Milan
next prev parent reply other threads:[~2010-03-06 19:25 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-03-06 17:45 [dm-crypt] Need some suggestions on large drives Scott Castaline
2010-03-06 19:25 ` Milan Broz [this message]
2010-03-07 1:27 ` Scott Castaline
2010-03-06 20:27 ` Arno Wagner
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=4B92AC30.5030304@redhat.com \
--to=mbroz@redhat.com \
--cc=dm-crypt@saout.de \
--cc=skotchman@gmail.com \
/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.