From: "Darrick J. Wong" <darrick.wong@oracle.com>
To: Eric Sandeen <sandeen@sandeen.net>
Cc: linux-xfs <linux-xfs@vger.kernel.org>
Subject: Re: xfs_scrub: call for testing
Date: Fri, 2 Feb 2018 13:51:30 -0800 [thread overview]
Message-ID: <20180202215130.GD4849@magnolia> (raw)
In-Reply-To: <e0ada9ef-aafb-5179-2729-447d67bd6265@sandeen.net>
On Fri, Feb 02, 2018 at 03:36:33PM -0600, Eric Sandeen wrote:
> Hey all -
>
> Darrick's done a great job with landing the xfs_scrub code in
> upstream kernel v4.15, and now merged on the for-next branch of
> xfsprogs to be released in xfsprogs-4.15.0.
>
> As with any big new body of code, there might be some rough
> edges despite best efforts. It'd be great to have people do
> some testing at this semi-early stage.
>
> The 10,000ft overview is that the new xfs_scrub command can
> /validate/ a lot of what's on disk while the filesystem
> is mounted; and the ability to repair will come in the future.
>
> For now, with the 4.15 kernel, functionality is limited to
> "scrubbing" meaning that it will simply check for consistency;
> in 4.15 there is no facility to repair or optimize/preen the
> filesystem.
FWIW the 4.16 kernel enhances scrub to cross-reference metadata with
each other for strengthened checking (not to mention picking up a pile
of bug fixes), so eventually you'll want to move on to that for testing.
Ofc we're not even to -rc1 yet so meh. :)
Longer term, I also have landed the dangerous_repair xfstest group that
uses xfs_db to fuzz every field in a filesystem to see if scrub will
complain and xfs_repair does something about it. Right now it's a bit
of a mess because it'll trip over scrub/repair not complaining about
fields that have no bad values (think inode timestamps) but I'm working
on a larger analysis of triaging known failures and fixing things that
the tools should catch but don't.
> 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?
Yes, please look at those things!
Thanks to Eric for reviewing all the userspace patches, and Dave and
Brian for reviewing all the kernel patches!
--D
> (haha no it won't eat your data)
> ((haha no can't promise that with 100% certainty))
>
> Thanks,
> -Eric
> --
> To unsubscribe from this list: send the line "unsubscribe linux-xfs" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
next prev parent reply other threads:[~2018-02-02 21:51 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 [this message]
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
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=20180202215130.GD4849@magnolia \
--to=darrick.wong@oracle.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).