From: "Arkadiusz Miśkiewicz" <arekm@maven.pl>
To: xfs@oss.sgi.com
Cc: Richard Scobie <richard@sauce.co.nz>
Subject: Re: [PATCH] xfs_repair is recommended over xfs_check.
Date: Mon, 21 Nov 2011 23:37:52 +0100 [thread overview]
Message-ID: <201111212337.52178.arekm@maven.pl> (raw)
In-Reply-To: <4ECAC84C.1070000@sauce.co.nz>
On Monday 21 of November 2011, Richard Scobie wrote:
> Is there currently now any situation where xfs_check would be used in
> preference to xfs_repair?
>
> If not, perhaps xfs_check could be deprecated.
There was a such idea but:
21:25 < sandeen_> well, it has a lot of use in xfstests, so it's nice to have
built & around, I think.
--
Arkadiusz Miśkiewicz PLD/Linux Team
arekm / maven.pl http://ftp.pld-linux.org/
_______________________________________________
xfs mailing list
xfs@oss.sgi.com
http://oss.sgi.com/mailman/listinfo/xfs
next prev parent reply other threads:[~2011-11-21 22:38 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-11-21 21:53 [PATCH] xfs_repair is recommended over xfs_check Richard Scobie
2011-11-21 22:37 ` Arkadiusz Miśkiewicz [this message]
2011-11-22 0:23 ` Dave Chinner
2011-11-22 4:32 ` Eric Sandeen
2011-11-22 5:27 ` Dave Chinner
-- strict thread matches above, loose matches on Subject: below --
2011-11-21 20:49 Arkadiusz Miśkiewicz
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=201111212337.52178.arekm@maven.pl \
--to=arekm@maven.pl \
--cc=richard@sauce.co.nz \
--cc=xfs@oss.sgi.com \
/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