[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <slrnelj5k3.7lr.olecom@flower.upol.cz>
Date: Tue, 14 Nov 2006 10:12:19 +0000
From: Oleg Verych <olecom@...wer.upol.cz>
To: Martin Braun <mbraun@...-hd.de>, David Chinner <dgc@....com>,
LKML <linux-kernel@...r.kernel.org>, xfs@....sgi.com
Subject: Re: xfs kernel BUG again in 2.6.17.11
Hallo.
On 2006-11-14, Martin Braun wrote:
> Hi David,
>
>
>> Have you managed to repair the filesystem since you first
>> reported this problem? I don't know the history of the bug
[Well. Just to help (probably) new developers, after Nathan left SGI.]
Here's FAQ node about bug:
http://oss.sgi.com/projects/xfs/faq.html#dir2
You can find fixes in .17 stable git tree.
If it was really just sparse annotations, they were obviously
fixed, i think. If not, meybe there are some new bugs.
> that's something I am not sure about, I have used the newest xfs_repair
> tools and it found and repaired some inodes. And for about two months
> there weren't any crashes.
+
> It seems that xfs_repair (2.8.10), did not find all of the errors of the FS.
> Is there a way to be sure that the FS is clean?
As in faq:
,--
.....
| Update: a fixed xfs_repair is now available; version 2.8.10 or later
| of the xfsprogs package contains the fixed version.
.....
| The xfs_check tool, or xfs_repair -n, should be able to detect any
| directory corruption.
`--
[]
> Normally the Kernel freezes/hangs completely, but I found two new
Do you mean panic or oops here, or just freeze?
____
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists