[dm-crypt] Status of trim for SSds?
list at eworm.de
Mon Jul 18 12:16:25 CEST 2011
Milan Broz <mbroz at redhat.com> 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
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...
More information about the dm-crypt