From: Brian Candler <B.Candler@pobox.com>
To: Ryan Lee <ryanlee.lahk@gmail.com>
Cc: xfs@oss.sgi.com
Subject: Re: [XFS] xfs_repair time how long it takes??
Date: Fri, 2 Mar 2012 16:18:08 +0000 [thread overview]
Message-ID: <20120302161808.GD12352@nsrc.org> (raw)
In-Reply-To: <CABF-5Wo1BRGgiy89PO+6sXzZ5ggFJYAXtXu+DA9hbEvfazFNqw@mail.gmail.com>
On Sat, Mar 03, 2012 at 12:48:06AM +0900, Ryan Lee wrote:
> You guys told me to use the "fsck.xfs".
No I didn't - I linked to the manpage. If you read it, you will see that it
says it does nothing at all.
It is purely a placeholder, for Linux systems which try to do fsck.<foo>
whenever they mount a filesystem of type <foo>.
The point is, you don't need it.
> Onething more, I already know about the problem with "xfs_repair", but
> I cound't find any other good solution to fix it until now.
>
> How can I fix it?
Probably you need to stop your journal from getting corrupted in the first
place. See the XFS FAQ:
http://xfs.org/index.php/XFS_FAQ#Q:_What_is_the_problem_with_the_write_cache_on_journaled_filesystems.3F
and the following 5 questions and answers. In particular make sure your
block driver has working write barrier support.
Final note: please don't reply to me without replying to the list as well. I
have been forwarding your replies to the list, but it is annoying to have to
do so. Your mail client probably has a 'reply to list' or 'group reply'
function you can use.
Regards,
Brian.
_______________________________________________
xfs mailing list
xfs@oss.sgi.com
http://oss.sgi.com/mailman/listinfo/xfs
next prev parent reply other threads:[~2012-03-02 16:18 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-03-02 13:09 [XFS] xfs_repair time how long it takes?? Ryan Lee
2012-03-02 14:01 ` Brian Candler
2012-03-02 14:26 ` Ryan
2012-03-02 14:52 ` Brian Candler
[not found] ` <4F50E246.4020502@sandeen.net>
2012-03-02 15:48 ` Ryan Lee
2012-03-02 15:56 ` Ryan Lee
2012-03-02 16:18 ` Brian Candler [this message]
2012-03-02 14:55 ` 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=20120302161808.GD12352@nsrc.org \
--to=b.candler@pobox.com \
--cc=ryanlee.lahk@gmail.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 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.