From: Oleg Verych <olecom@flower.upol.cz>
To: Martin Braun <mbraun@uni-hd.de>, David Chinner <dgc@sgi.com>,
LKML <linux-kernel@vger.kernel.org>,
xfs@oss.sgi.com
Subject: Re: xfs kernel BUG again in 2.6.17.11
Date: Tue, 14 Nov 2006 10:12:19 +0000 [thread overview]
Message-ID: <slrnelj5k3.7lr.olecom@flower.upol.cz> (raw)
In-Reply-To: 45598B07.6080401@uni-hd.de
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?
____
next prev parent reply other threads:[~2006-11-14 10:06 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <44E1D9CA.30805@uni-hd.de>
2006-08-16 0:11 ` kernel BUG at <bad filename>:50307! Nathan Scott
[not found] ` <44EB228F.6020903@uni-hd.de>
[not found] ` <20060823134211.E2968256@wobbly.melbourne.sgi.com>
[not found] ` <45583ABE.6080909@uni-hd.de>
2006-11-14 4:00 ` xfs kernel BUG again in 2.6.17.11 David Chinner
2006-11-14 9:23 ` Martin Braun
2006-11-14 10:12 ` Oleg Verych [this message]
2006-11-14 10:31 ` Martin Braun
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=slrnelj5k3.7lr.olecom@flower.upol.cz \
--to=olecom@flower.upol.cz \
--cc=dgc@sgi.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mbraun@uni-hd.de \
--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