Clemens Fruhwirth schrieb: > I recently switched to an LVM setup that is backed by a single > physical volume accessed via dm-crypt. I have seen strange corruptions > with cryptsetup, incompletely written headers that were reproducible > 4/5 of the time. > > I blamed the fact that I had orphaned mappings to the corrupting > device (left overs of temporary-cryptsetup-mapping). The upcoming > version of cryptsetup will require exclusive access to the underlying > device and also trap ctrl-c's so that these mappings are > removed. After hacking these sanity checks into cryptsetup, this thing > went away. But it doesn't look like that this was the thing to blame. > > Yesterday I renamed the LVM volume (vgrename), and after that the LVM > header was corrupted. LVM is in the same position as cryptsetup > (although it does not know). cryptsetup sets up a temporary mapping > and opens this raw block dev to write headers. LVM gets a block device > and also writes header by opening the raw block device. So these > positions are identical when you hand an encrypted volume to LVM as > physical volume. I have used such setups (LVM, combined with LUKS) with 2.6.2[0-3] and maybe earlier kernels. I am unsure about which version I started with though (2.6.18? 2.6.19?). I never had any of the issues that you describe, and I did lots of lvresize operations and similar. --------------------------------------------------------------------- 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
