From: Ulli Horlacher <framstag@rus.uni-stuttgart.de>
To: Btrfs BTRFS <linux-btrfs@vger.kernel.org>
Subject: Re: weekly fstrim (still) necessary?
Date: Mon, 22 Jun 2020 16:02:34 +0200 [thread overview]
Message-ID: <20200622140234.GA4512@tik.uni-stuttgart.de> (raw)
In-Reply-To: <CAJCQCtQ8GFAdg2HJY_HqDgW8WAp5L1GoLbKqUN2mZ7s_kS-8XA@mail.gmail.com>
On Sun 2020-06-21 (18:57), Chris Murphy wrote:
> > > You need to check fstrim.timer, which in turn triggers fstrim.service.
> >
> > root@fex:~# cat /lib/systemd/system/fstrim.timer
> >
> > root@fex:~# cat /lib/systemd/system/fstrim.service
> I'm familiar with the contents of the files. Do you have a question?
You have deleted my question, it have asked:
This means: an extra fstrim (via btrfsmaintenance script, etc) is
unnecessary?
--
Ullrich Horlacher Server und Virtualisierung
Rechenzentrum TIK
Universitaet Stuttgart E-Mail: horlacher@tik.uni-stuttgart.de
Allmandring 30a Tel: ++49-711-68565868
70569 Stuttgart (Germany) WWW: http://www.tik.uni-stuttgart.de/
REF:<CAJCQCtQ8GFAdg2HJY_HqDgW8WAp5L1GoLbKqUN2mZ7s_kS-8XA@mail.gmail.com>
next prev parent reply other threads:[~2020-06-22 14:02 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-06-21 5:42 weekly fstrim (still) necessary? Ulli Horlacher
2020-06-21 7:01 ` Andrei Borzenkov
2020-06-21 16:24 ` Lukas Tribus
2020-06-21 18:19 ` Adam Borowski
2020-06-21 19:39 ` Chris Murphy
2020-06-21 23:52 ` Ulli Horlacher
2020-06-21 23:57 ` Chris Murphy
2020-06-22 0:06 ` Ulli Horlacher
2020-06-22 0:57 ` Chris Murphy
2020-06-22 14:02 ` Ulli Horlacher [this message]
2020-06-22 14:23 ` David Sterba
2020-06-22 15:56 ` Chris Mason
2020-06-26 12:08 ` Fwd: " Tim Cuthbertson
2020-06-26 15:40 ` Chris Mason
2020-06-26 16:40 ` Chris Murphy
2020-06-26 16:48 ` Chris Mason
2020-06-26 19:32 ` Tim Cuthbertson
[not found] ` <CAAKzf7kMFqkrQyRzJ6WHVE95PBm2e0BX+QBua-2-rasp=BR7FQ@mail.gmail.com>
2020-06-26 19:33 ` Fwd: " Tim Cuthbertson
[not found] ` <00D64498-C734-4D08-8FBE-019B7292BE8E@fb.com>
2020-06-26 19:52 ` Tim Cuthbertson
2020-06-26 20:18 ` Remi Gauvin
2020-06-26 20:49 ` Roman Mamedov
2020-06-27 12:13 ` Jan Killius
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=20200622140234.GA4512@tik.uni-stuttgart.de \
--to=framstag@rus.uni-stuttgart.de \
--cc=linux-btrfs@vger.kernel.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