From: Emmanuel Florac <eflorac@intellique.com>
To: Christoph Hellwig <hch@lst.de>
Cc: xfs@oss.sgi.com
Subject: Re: xfs_check
Date: Wed, 28 May 2008 10:20:38 +0200 [thread overview]
Message-ID: <20080528102038.768dfd93@galadriel.home> (raw)
In-Reply-To: <20080527162605.GA30344@lst.de>
Le Tue, 27 May 2008 18:26:05 +0200 vous écriviez:
> Is there any reason
> why we shouldn't simply kill xfs_check and replaced it with a wrapper
> around xfs_repair?
I may add that I hardly even had any filesystem recently small enough
to fit xfs_check hunger for memory. All attempts to use xfs_check
invariably ended with "out of memory" for 5 years or more. Actually
IIRC I used xfs_check succesfully only on IRIX, back in the time of
9GB usrroot drives :)
--
--------------------------------------------------
Emmanuel Florac www.intellique.com
--------------------------------------------------
prev parent reply other threads:[~2008-05-28 8:23 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-05-27 16:26 xfs_check Christoph Hellwig
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 ` Emmanuel Florac [this message]
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=20080528102038.768dfd93@galadriel.home \
--to=eflorac@intellique.com \
--cc=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.