From: "Darrick J. Wong" <darrick.wong@oracle.com>
To: Emmanuel Florac <eflorac@intellique.com>
Cc: Eric Sandeen <sandeen@sandeen.net>,
linux-xfs <linux-xfs@vger.kernel.org>
Subject: Re: xfs_scrub: call for testing
Date: Mon, 5 Feb 2018 14:39:59 -0800 [thread overview]
Message-ID: <20180205223959.GJ4849@magnolia> (raw)
In-Reply-To: <20180205180807.261e822f@harpe.intellique.com>
On Mon, Feb 05, 2018 at 06:08:07PM +0100, Emmanuel Florac wrote:
> Le Mon, 5 Feb 2018 09:49:41 -0600
> Eric Sandeen <sandeen@sandeen.net> écrivait:
>
> > >
> > > Wouldn't it be better to remove the parts about repairing the
> > > filesystem in the documentation? The man page states that it *can't*
> > > repair the filesystem, but nonetheless explains under which
> > > circumstances it *won't* be able to repair (in some theoretical
> > > future version with repair capabilities, I suppose). Ditto with the
> > > -n and -y option, I suppose they're both basically noop at the
> > > moment? That's quite unclear what it actually does.
> >
> > I'll take another look at the manpage. The userspace tool today /can/
> > do some degree of optimization or repair if the kernel supports it,
> > so I was reluctant to suggest removing all such language.
> >
> > So, "-n" is not a no-op, it's a check-only ("scrub") pass vs. the
> > default no-argument action of "optimizing," or the extra -y action
> > which would repair. If that's not all clear, I'd appreciate
> > suggestions to clean it up.
> >
>
> Now I'm wondering: is the default option of "optimizing" really
> useful? Wouldn't it be better to simply have a check-only (-n) version,
> and a full-fledged version when given no argument?
> Or maybe do a simple optimisation, optionally, when given the '-y' (or
> some other flag) option?
>
> I say that after having a look at man pages from some comparable
> utilities, namely xfs_repair, btrfs_scrub and "zpool scrub", who all
> default to "full operation" without options.
I don't care /that/ much about what 'zpool scrub' does, but I do see
your point that from the admin's perspective either we fix everything or
we don't, so there's no need for a -y and we can do what repair does (-n
means dry run, lack of -n means fix it).
--D
>
> --
> ------------------------------------------------------------------------
> Emmanuel Florac | Direction technique
> | Intellique
> | <eflorac@intellique.com>
> | +33 1 78 94 84 02
> ------------------------------------------------------------------------
next prev parent reply other threads:[~2018-02-05 22:40 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-02-02 21:36 xfs_scrub: call for testing Eric Sandeen
2018-02-02 21:51 ` Darrick J. Wong
2018-02-05 15:10 ` Emmanuel Florac
2018-02-05 15:49 ` Eric Sandeen
2018-02-05 16:44 ` Darrick J. Wong
2018-02-05 16:55 ` Eric Sandeen
2018-02-05 22:40 ` Darrick J. Wong
2018-02-05 17:08 ` Emmanuel Florac
2018-02-05 22:39 ` Darrick J. Wong [this message]
2018-02-15 18:18 ` Emmanuel Florac
2018-04-02 0:10 ` Chris Murphy
2018-04-02 2:01 ` Eric Sandeen
2018-04-02 4:23 ` Chris Murphy
2018-04-02 2:44 ` Darrick J. Wong
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=20180205223959.GJ4849@magnolia \
--to=darrick.wong@oracle.com \
--cc=eflorac@intellique.com \
--cc=linux-xfs@vger.kernel.org \
--cc=sandeen@sandeen.net \
/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;
as well as URLs for NNTP newsgroup(s).