public inbox for util-linux@vger.kernel.org
 help / color / mirror / Atom feed
From: "Thomas Bächler" <thomas@archlinux.org>
To: "Ruediger Meier" <sweet_f_a@gmx.de>,
	"Thomas Bächler" <thomas@archlinux.org>
Cc: Karel Zak <kzak@redhat.com>, util-linux@vger.kernel.org
Subject: Re: [PATCH] fstrim: add systemd units
Date: Wed, 09 Apr 2014 17:24:42 +0200	[thread overview]
Message-ID: <5345663A.1050403@archlinux.org> (raw)
In-Reply-To: <201404091716.05131.sweet_f_a@gmx.de>

[-- Attachment #1: Type: text/plain, Size: 1978 bytes --]

Am 09.04.2014 17:16, schrieb Ruediger Meier:
> On Wednesday 09 April 2014, Thomas Bächler wrote:
>> Am 09.04.2014 14:12, schrieb Ruediger Meier:
>>>> well, "fstrim -a" contains heruistic to select the right filestems
>>>> (it really does not call trim for all devices), it has been
>>>> implemented to *avoid* sysadmins creativity. If you don't like it,
>>>> you can use "fstrim <device>" (for example from crontab).
>>>
>>> I'd like the documentation more detailed.
>>> Does it really run on all mounts or only /etc/fstab?
>>> Does it write on automounted devices which are probably not owned
>>> by the admin? Does it affect read-only mounts?
>>
>> The documentation is precise here:
>>
>> 'Trim all mounted filesystems on devices that support the discard
>> operation.'
> 
> If this is 100% true then Karel's statement 10 lines above would be 
> wrong.

There is no contradiction between this and what Karel said. I think you
are confused and should read both statements again.

> Also this doc line indicates that even read-only mounts could be trimmed 
> (if FS supports it) which would be at least dangerous if it runs 
> automatically while admin is trying to repair a broken filesystem.

The documentation says nothing about excluding read-only file systems,
that should probably be changed (but it is not something that I,
personally, am terribly concerned about).

>> It is not complicated, it is just a task that shouldn't be repeated
>> countless times.
> 
> Now you still need to enable it "countless times" which I would do using 
> rsync or git anyway like I would sync self created timers, crontabs or 
> whatever config files with same effort.

This is getting annoying. It is your opinion that we should not add
useful things because we haven't done so in the past, or because someone
might want to do it slightly differently.

I submitted it, Karel added it, period. There's no point continuing this
argument.



[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 901 bytes --]

  reply	other threads:[~2014-04-09 15:24 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 [this message]
2014-04-09 15:44                       ` Ruediger Meier
2014-04-09 14:02               ` Markus Trippelsdorf
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=5345663A.1050403@archlinux.org \
    --to=thomas@archlinux.org \
    --cc=kzak@redhat.com \
    --cc=sweet_f_a@gmx.de \
    --cc=util-linux@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