At Wed, 6 Feb 2008 23:29:31 +0100,
Jonas Meurer wrote:
> Clemens, I believe that both options are not meant to be used on luks
> devices. What do you think about implementing a check to cryptsetup
> which simply prohibits resize/reload if executed on a luks device?
Yes, that should be possible quite easily. iirc there is a function in
cryptsetup (use for isLuks) to check exactly that.
> Or is it technically possible to adapt the options for luks devices?
Yes.
>From a quick glance at the code, ('reload' is just a special variant
of 'create' that does not fail when the device exists) it looks like
reload expects you to resupply all options used in the mapping. As the
LUKS payload starts with an offset into the underlying block device,
not supplying --offset to reload will trash the partition for sure.
So either we change the semantics of reload to retain existing options
(so not supplying --offset does not reset the offset of the mapping
back to zero), or we create something special for LUKS. luksReload?
Maybe not.
I'm at the moment not sure what's wrong with resize though, I gotta
look at that in more detail.
--
Fruhwirth Clemens - http://clemens.endorphin.org
---------------------------------------------------------------------
dm-crypt mailing list - http://www.saout.de/misc/dm-crypt/
To unsubscribe, e-mail: dm-crypt-unsubscribe@xxxxxxxx
For additional commands, e-mail: dm-crypt-help@xxxxxxxx
