From: Danny Milosavljevic <dannym@scratchpost.org>
To: "Ludovic Courtès" <ludo@gnu.org>
Cc: guix-devel@gnu.org
Subject: Re: fstrim and SSDs and cron; was: Re: cron-service
Date: Wed, 18 May 2016 07:21:18 +0200 [thread overview]
Message-ID: <20160518072118.6039bd22@scratchpost.org> (raw)
In-Reply-To: <87zirotm2n.fsf@gnu.org>
> I had never thought of it, but maybe it’s a good idea. How do other
> distros handle it?
On <https://askubuntu.com/questions/18903/how-to-enable-trim> they say:
>Ubuntu 14.10 onwards:
>In Ubuntu 14.10 and 15.04, TRIMming happens automatically every week on all SSDs supported by fstrim.
>$ tail -n1 /etc/cron.weekly/fstrim
>/sbin/fstrim --all || true
>Automatic TRIM (Deprecated, Slow):
> [fstab...]
>Encrypted Filesystems
>The last step is not enough though. As long as LUKS is not aware that you want to use TRIM it will effectively block all TRIM operations coming from the LVM partition's file system, for security reasons. Add discard parameter to the cryptdevice options in /etc/crypttab to make LUKS accept the discard behavior of the LVM partition.
>sda5_crypt UUID=e364d03f-[...]6cd7e none luks,discard
More info about the latter:
http://blog.neutrino.es/2013/howto-properly-activate-trim-for-your-ssd-on-linux-fstrim-lvm-and-dmcrypt/
Note that guix /gnu/store/8vg9124cgm8d36zsy9ldcw53b1vrfy2w-lvm2-2.02.109/etc/lvm/lvm.conf explicitly disables (!) "discard".
next prev parent reply other threads:[~2016-05-18 5:21 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-04-30 17:27 cron-service Danny Milosavljevic
2016-05-01 13:14 ` cron-service Ludovic Courtès
2016-05-17 17:28 ` fstrim and SSDs and cron; was: cron-service Danny Milosavljevic
2016-05-17 21:24 ` Ludovic Courtès
2016-05-18 1:56 ` Thompson, David
2016-05-18 5:09 ` Danny Milosavljevic
2016-05-18 5:21 ` Danny Milosavljevic [this message]
2016-05-18 8:50 ` Efraim Flashner
2016-06-23 8:18 ` mcron service Ludovic Courtès
2016-06-24 5:59 ` Danny Milosavljevic
2016-06-24 12:00 ` Ludovic Courtès
2016-06-24 14:18 ` Alex Kost
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20160518072118.6039bd22@scratchpost.org \
--to=dannym@scratchpost.org \
--cc=guix-devel@gnu.org \
--cc=ludo@gnu.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this external index
https://git.savannah.gnu.org/cgit/guix.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.