From: Troy McCorkell <tdm@sgi.com>
To: xfs@oss.sgi.com, Chandra Seetharaman <sekharan@us.ibm.com>,
Ben Myers <bpm@sgi.com>
Subject: Re: Deprecating xfs_check
Date: Thu, 11 Apr 2013 18:01:12 -0500 [thread overview]
Message-ID: <516740B8.4030704@sgi.com> (raw)
In-Reply-To: <20130411221754.GI22182@sgi.com>
On 04/11/2013 05:17 PM, Ben Myers wrote:
> Hey Chandra,
>
> On Thu, Apr 11, 2013 at 04:45:08PM -0500, Chandra Seetharaman wrote:
>> Hello All,
>>
>> Alex Elder mentioned about deprecating xfs_check, and he suggested is to
>> replace xfs_check command with a script, that says xfs_check is
>> deprecated, use "xfs_repair -n".
>>
>> Sounds ok ?
>>
>> Let me know if it is not the right approach.
> That sounds ok to me. You might also consider making xfs_check a hardlink to
> xfs_repair and varying the behavior based on program name. Then xfs_check ==
> xfs_repair -n.
>
> Regards,
> Ben
>
> _______________________________________________
> xfs mailing list
> xfs@oss.sgi.com
> http://oss.sgi.com/mailman/listinfo/xfs
Does "xfs_repair -n" need to provide all of the functionality that xfs_check
provides before it is replaced?
xfs_check can be run on a filesystem mounted read-only. xfs_repair -n
can not.
xfs_check has two options:
-i ino Specifies verbose behavior for the specified inode ino.
-b bno Specifies verbose behavior for the specific filesystem
block at bno.
which are not available with xfs_repair.
-Troy
_______________________________________________
xfs mailing list
xfs@oss.sgi.com
http://oss.sgi.com/mailman/listinfo/xfs
next prev parent reply other threads:[~2013-04-11 23:01 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-04-11 21:45 Deprecating xfs_check Chandra Seetharaman
2013-04-11 22:17 ` Ben Myers
2013-04-11 23:01 ` Troy McCorkell [this message]
2013-04-12 1:04 ` Dave Chinner
2013-04-12 14:41 ` Troy McCorkell
2013-04-16 17:27 ` Chandra Seetharaman
2013-04-20 19:14 ` Alex Elder
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=516740B8.4030704@sgi.com \
--to=tdm@sgi.com \
--cc=bpm@sgi.com \
--cc=sekharan@us.ibm.com \
--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