| To: | Ryan Lee <ryanlee.lahk@xxxxxxxxx> |
|---|---|
| Subject: | Re: [XFS] xfs_repair time how long it takes?? |
| From: | Brian Candler <B.Candler@xxxxxxxxx> |
| Date: | Fri, 2 Mar 2012 16:18:08 +0000 |
| Cc: | xfs@xxxxxxxxxxx |
| Dkim-signature: | v=1; a=rsa-sha1; c=relaxed; d=pobox.com; h=date:from:to :cc:subject:message-id:references:mime-version:content-type :in-reply-to; s=sasl; bh=h2xXl+q5sELDuEwVMsooQc8+CDs=; b=F+t1gCA VUnCGcHlz+r6abNtzB+oYO8/vDZ9237Am0NR6qxvh3vHHnZlLgpAA0b8k8ws7plY C05/1mEBVZDQR41rVrj0b9Pyz66rcSW534BSfXIgyChuJhP+qT6aOyUyk4U10Ukd TPBFbQR68VA9JZq41/7VtSJnUKOiaTWUSjic= |
| Domainkey-signature: | a=rsa-sha1; c=nofws; d=pobox.com; h=date:from:to:cc :subject:message-id:references:mime-version:content-type :in-reply-to; q=dns; s=sasl; b=eg1abSI5yGnUjhHqSC8FSc9bXILniW7dI YaL0TUi9xKWmm9X0aNwjEfzCDUJUfjt72nCBbkBBc9Rz16Ady+XJvN72wW7R78pJ Qcfx/CzRR+dVZAYxOYeNlysiBUCJu3FSt91eXA13xl4pkBbMQZ0g5AAl2grvAzqy pOmPKR0r74= |
| In-reply-to: | <CABF-5Wo1BRGgiy89PO+6sXzZ5ggFJYAXtXu+DA9hbEvfazFNqw@xxxxxxxxxxxxxx> |
| References: | <CABF-5WptGU3vmScFcpHVstd2UZfCAqiY4dGvL=_1+feFvYuS6g@xxxxxxxxxxxxxx> <20120302140145.GA11911@xxxxxxxx> <37B5727D-1E3B-4A96-BF7F-4CA6DAF9B63C@xxxxxxxxx> <4F50E246.4020502@xxxxxxxxxxx> <CABF-5Wo1BRGgiy89PO+6sXzZ5ggFJYAXtXu+DA9hbEvfazFNqw@xxxxxxxxxxxxxx> |
| User-agent: | Mutt/1.5.21 (2010-09-15) |
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. |
| <Prev in Thread] | Current Thread | [Next in Thread> |
|---|---|---|
| ||
| Previous by Date: | Re: [XFS] xfs_repair time how long it takes??, Ryan Lee |
|---|---|
| Next by Date: | Re: [PATCH 6/8] xfs: make xfs_inode_item_size idempotent, Mark Tinguely |
| Previous by Thread: | Re: [XFS] xfs_repair time how long it takes??, Ryan Lee |
| Next by Thread: | Re: [XFS] xfs_repair time how long it takes??, Eric Sandeen |
| Indexes: | [Date] [Thread] [Top] [All Lists] |