From: Emmanuel Florac <eflorac@intellique.com>
To: Eric Sandeen <sandeen@sandeen.net>
Cc: linux-xfs <linux-xfs@vger.kernel.org>
Subject: Re: xfs_scrub: call for testing
Date: Mon, 5 Feb 2018 16:10:49 +0100 [thread overview]
Message-ID: <20180205161049.7e22aa09@harpe.intellique.com> (raw)
In-Reply-To: <e0ada9ef-aafb-5179-2729-447d67bd6265@sandeen.net>
[-- Attachment #1: Type: text/plain, Size: 1807 bytes --]
Le Fri, 2 Feb 2018 15:36:33 -0600
Eric Sandeen <sandeen@sandeen.net> écrivait:
> I'd really value feedback on scrub as it stand at this point -
> Is the documentation clear? Is the output correct? Do the
> tool's arguments make sense? Does it segfault? Does it
> find real errors? Does it crash your kernel? Does it
> eat your data?
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.
Regarding FITRIM for flash storage, I think most people refers to it as
"TRIM", not the ioctl name FITRIM. Using "TRIM" would probably be more
understandable IMO.
Because I'm such a funny boy, I just wanted to see what happens when
running xfs_scrub on an unsupported kernel. On both a 4.14.x and a
3.18.x it seems about right:
root@bareos16:~# ./xfs_scrub /mnt/raid/
EXPERIMENTAL xfs_scrub program in use! Use at your own risk!
Error: /mnt/raid: Kernel metadata scrubbing facility is not available.
Info: /mnt/raid: Scrub aborted after phase 1.
/mnt/raid: 2 errors found.
I don't have any system running 4.15 to test its effects, but I'll do
as soon as possible.
--
------------------------------------------------------------------------
Emmanuel Florac | Direction technique
| Intellique
| <eflorac@intellique.com>
| +33 1 78 94 84 02
------------------------------------------------------------------------
[-- Attachment #2: Signature digitale OpenPGP --]
[-- Type: application/pgp-signature, Size: 181 bytes --]
next prev parent reply other threads:[~2018-02-05 15:10 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 [this message]
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
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=20180205161049.7e22aa09@harpe.intellique.com \
--to=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).