From: Eric Sandeen <sandeen@sandeen.net>
To: hank peng <pengxihan@gmail.com>
Cc: linux-xfs@oss.sgi.com
Subject: Re: can xfs_repair guarantee a complete clean filesystem?
Date: Mon, 30 Nov 2009 23:58:15 -0600 [thread overview]
Message-ID: <4B14B077.5090500@sandeen.net> (raw)
In-Reply-To: <389deec70911302037v19764c2cr7686b353c5e933fa@mail.gmail.com>
hank peng wrote:
> 2009/12/1 Eric Sandeen <sandeen@sandeen.net>:
>> hank peng wrote:
>>> When using xfs_repair, I want my XFS filesystem complete clean and
>>> continue to work even if some files lost. Becase we use XFS in low-end
>>> NAS box, customers want a tool to repair the filesystem when it has
>>> problem and they allow some files be lost and don't want the whole
>>> system to stop.
>>> So, I wonder if xfs_repair or some other tools can satisfy this funciton?
>>>
>> Yes, that is exactly its purpose (any potential bugs notwithstanding...)
>>
> Thanks for your reply.
> Is there some points I should notice about when using xfs_repair? I
> used to encounter some cases in which xfs_repair complete successfully
> but some errors like "Corrupt in memory detected" occured when the
> filesytem is put into online for short time.
It's possible that you encountered a bug (in xfs or elsewhere), or
bad hardware...
> Should I reboot the machine and use xfs_repair before the damaged
> filesystem is used, or some other options I should use?
Just unmount the filesystem, run repair, and remount.
> In addition, I googled some information and found that some people say
> xfs_check should be used before xfs_repair, is it right?
There's no need; xfs_check doesn't scale very well, and xfs_repair -n will do
a check-only run if that's what you want.
xfs_check checks a little more than xfs_repair, but xfs_repair simply
rebuilds those things it doesn't check in any case.
-Eric
>> -Eric
>>
>
>
>
_______________________________________________
xfs mailing list
xfs@oss.sgi.com
http://oss.sgi.com/mailman/listinfo/xfs
next prev parent reply other threads:[~2009-12-01 5:57 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-12-01 2:05 can xfs_repair guarantee a complete clean filesystem? hank peng
2009-12-01 3:54 ` Eric Sandeen
2009-12-01 4:37 ` hank peng
2009-12-01 5:58 ` Eric Sandeen [this message]
2009-12-01 6:34 ` hank peng
2009-12-01 14:43 ` Eric Sandeen
2009-12-01 15:32 ` hank peng
2009-12-01 15:44 ` Eric Sandeen
2009-12-02 0:46 ` hank peng
2009-12-02 1:08 ` Eric Sandeen
2009-12-02 1:36 ` hank peng
2009-12-02 2:39 ` hank peng
2009-12-02 3:52 ` Eric Sandeen
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=4B14B077.5090500@sandeen.net \
--to=sandeen@sandeen.net \
--cc=linux-xfs@oss.sgi.com \
--cc=pengxihan@gmail.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