On 03/10/2011 07:06 PM, Robert.Heinzmann@xxxxxxxxxxxxxxx wrote: > Do you see any problems (from the dm_crypt side) with this setup in > terms of deadlocks, or unsupported stacking or is this a "supposed > to work" configuration ? Stacking should work without problems. Just when online resizing you need additional step when resizing crypt device (cryptsetup resize <dev> is for online resize. Or just activate/ deactivate and it loads new size.) I depends on your preference if you want use LVM over LUKS or vice versa, both works. Basically stacking is design feature of device-mapper. > I know that device mapper always causes performance penalty because > of missing barrier support (earlier Kernels) and I/O splitting in 4k > units, however I have a BBU, so not a problem really and performance > penalty is allowed. Barrier (or flush) is fully supported in recent kernels, even for dmcrypt. Split to 4k unit is also solved long time ago, dmcrypt provides io merge functionality so even when stacking devices it uses "ideal" io size - depends on underlying device and io pattern. So it depends on which distro and kernel you are using. (I guess you are using RHEL5 clone, even there it can be configure efficiently. In fact many users have very similar configuration like you described.) Milan _______________________________________________ dm-crypt mailing list dm-crypt@xxxxxxxx http://www.saout.de/mailman/listinfo/dm-crypt
