Christian Hesse <list@xxxxxxxx> on Mon, 18 Jul 2011 12:16:25 +0200: > Milan Broz <mbroz@xxxxxxxxxx> on Mon, 18 Jul 2011 12:04:18 +0200: > > On 07/18/2011 10:45 AM, Christian Hesse wrote: > > > If I understand correctly the table reload suspends my device? With the > > > root partition inside the crypt device I would have to do this in > > > initram disk I think... > > > > No. "load" will just load table into inactive slot. Following "resume" > > will implicitly suspend device and immediately resume with new table (in > > kernel) so it should be safe. > > Ok, good to know. > > > > Perhaps I really should wait for support in cryptsetup. :D > > > > In devel tree is already "--allow-discard" option for luksOpen/create > > command. > > Already compiled. ;) > > > (But I guess /etc/ctypttab need new option here as well for system > > devices but that's must be fixed by initscripts. There will be no > > cryptsetup command to enable it on-fly, just for activation commands.) > > I do not use crypttab. All I need is a modified hook in my initrd... Everything seems to work here... 14:50:07 root@leda:~# dmsetup table /dev/mapper/cvg 0 922742784 crypt aes-cbc-essiv:sha256 0000000000000000000000000000000000000000000000000000000000000000 0 8:2 4096 1 allow_discards 14:51:48 root@leda:~# dumpe2fs /dev/cvg/log | grep discard dumpe2fs 1.41.14 (22-Dec-2010) Default mount options: discard However mount does not list the discard option... Even when explicitly remounting. Is this because it is the default mount option? 14:51:52 root@leda:~# mount | grep log /dev/mapper/cvg-log on /var/log type ext4 (rw,relatime,user_xattr,acl,barrier=1,data=ordered) Thanks again for you work! -- Schoene Gruesse Chris _______________________________________________ dm-crypt mailing list dm-crypt@xxxxxxxx http://www.saout.de/mailman/listinfo/dm-crypt
