From: Christoph Hellwig <hch@lst.de>
To: xfs@oss.sgi.com
Subject: xfs_check
Date: Tue, 27 May 2008 18:26:05 +0200 [thread overview]
Message-ID: <20080527162605.GA30344@lst.de> (raw)
In the past we had quite a few cases where we told people to run
xfs_repair -n instead of xfs_check. I think that makes a lot of sense
because xfs_repair -n generally gives output at least as useful as
xfs_check if not more so and also is a lot faster. Is there any reason
why we shouldn't simply kill xfs_check and replaced it with a wrapper
around xfs_repair?
next reply other threads:[~2008-05-27 16:25 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-05-27 16:26 Christoph Hellwig [this message]
2008-05-27 16:48 ` xfs_check Eric Sandeen
2008-05-27 16:50 ` xfs_check Chris Wedgwood
2008-05-27 16:55 ` xfs_check Eric Sandeen
2008-05-27 23:50 ` xfs_check Barry Naujok
2008-05-27 23:21 ` xfs_check Dave Chinner
2008-05-27 23:49 ` xfs_check Barry Naujok
2008-05-28 8:20 ` xfs_check Emmanuel Florac
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=20080527162605.GA30344@lst.de \
--to=hch@lst.de \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.