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 14:01:45 +0000 [thread overview]
Message-ID: <20120302140145.GA11911@nsrc.org> (raw)
In-Reply-To: <CABF-5WptGU3vmScFcpHVstd2UZfCAqiY4dGvL=_1+feFvYuS6g@mail.gmail.com>
On Fri, Mar 02, 2012 at 10:09:56PM +0900, Ryan Lee wrote:
> The problem is the taking time with xfs_repair like this "]# xfs_repair
> -P -L /dev/sda2" is to long to wait in our embedded system and for me,
> so the booing time is increasing around 2 minutes totally.
Why do you feel you need to run xfs_repair on every boot? Regular Linux
systems do not attempt this, the same as they don't force a full "e2fsck -f"
on every boot.
http://linux.die.net/man/8/fsck.xfs
_______________________________________________
xfs mailing list
xfs@oss.sgi.com
http://oss.sgi.com/mailman/listinfo/xfs
next prev parent reply other threads:[~2012-03-02 14:01 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 [this message]
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
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=20120302140145.GA11911@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox