From: Markus Trippelsdorf <markus@trippelsdorf.de>
To: Karel Zak <public-kzak-H+wXaHxf7aLQT0dZR+AlfA@plane.gmane.org>
Cc: "Ruediger Meier" <public-sweet_f_a-Mmb7MZpHnFY@plane.gmane.org>,
"Thomas Bächler"
<public-thomas-fd97jBR+K/6hPH1hqNUYSQ@plane.gmane.org>,
public-util-linux-u79uwXL29TY76Z2rM5mHXA@plane.gmane.org
Subject: Re: [PATCH] fstrim: add systemd units
Date: Wed, 9 Apr 2014 16:02:40 +0200 [thread overview]
Message-ID: <20140409140240.GA26270@x4> (raw)
In-Reply-To: <20140409110251.GT22126@x2.net.home>
On 2014.04.09 at 13:02 +0200, Karel Zak wrote:
> On Wed, Apr 09, 2014 at 12:07:56PM +0200, Ruediger Meier wrote:
> > Actually I think daily "fstrim -a" IS not a good idea for most of my
> > systems
>
> install service != enable (this is important detail, I'll never agree
> with automatically enabled services).
>
> BTW, why IS not a good idea for your systems?
The fixed interval is problematic. There are SSD devices out there that
suffer (their flash cells die out faster) when they get trimmed too
often. A good rule of thumb is to trim once you have written the same
amount as you have free space on your device. Obviously, that interval
varies for every user (e.g. it's one week in my case).
--
Markus
next prev parent reply other threads:[~2014-04-09 14:04 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-04-03 21:41 [PATCH] fstrim: add systemd units Thomas Bächler
2014-04-07 10:43 ` Karel Zak
2014-04-08 10:25 ` Ruediger Meier
2014-04-08 10:57 ` Thomas Bächler
2014-04-08 12:07 ` Ruediger Meier
2014-04-08 15:42 ` Dave Reisner
2014-04-08 17:12 ` Ruediger Meier
2014-04-09 7:52 ` Karel Zak
2014-04-09 10:07 ` Ruediger Meier
2014-04-09 11:02 ` Karel Zak
2014-04-09 12:12 ` Ruediger Meier
2014-04-09 12:49 ` Thomas Bächler
2014-04-09 15:16 ` Ruediger Meier
2014-04-09 15:24 ` Thomas Bächler
2014-04-09 15:44 ` Ruediger Meier
2014-04-09 14:02 ` Markus Trippelsdorf [this message]
2014-04-09 15:48 ` Ruediger Meier
2014-04-09 15:55 ` Markus Trippelsdorf
2014-04-09 18:39 ` Theodore Ts'o
2014-04-10 8:05 ` Karel Zak
2014-04-10 9:17 ` Ruediger Meier
2014-04-10 12:49 ` Karel Zak
2014-04-10 13:16 ` Ruediger Meier
2014-04-10 13:22 ` Ruediger Meier
2014-04-08 17:26 ` Karel Zak
2014-04-08 17:30 ` Thomas Bächler
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=20140409140240.GA26270@x4 \
--to=markus@trippelsdorf.de \
--cc=public-kzak-H+wXaHxf7aLQT0dZR+AlfA@plane.gmane.org \
--cc=public-sweet_f_a-Mmb7MZpHnFY@plane.gmane.org \
--cc=public-thomas-fd97jBR+K/6hPH1hqNUYSQ@plane.gmane.org \
--cc=public-util-linux-u79uwXL29TY76Z2rM5mHXA@plane.gmane.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.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox