From: Stian Jordet <liste@jordet.net>
To: Martin Steigerwald <Martin@lichtvoll.de>
Cc: xfs@oss.sgi.com
Subject: Re: xfs bug in 2.6.17.9?
Date: Fri, 25 Aug 2006 01:45:33 +0200 [thread overview]
Message-ID: <1156463133.19666.4.camel@localhost.localdomain> (raw)
In-Reply-To: <200608241429.14277.Martin@lichtvoll.de>
tor, 24,.08.2006 kl. 14.29 +0200, skrev Martin Steigerwald:
> It looks to me that the directory corruption bug in kernel 2.6.17 upto
> 2.6.17.6 hit you: Did you use a 2.6.17 kernel < 2.6.17.7 before?
>
> See
>
> http://oss.sgi.com/projects/xfs/faq.html#dir2
> http://bugzilla.kernel.org/show_bug.cgi?id=6757
>
> Try xfs_check and if it finds errors xfs_repair.
>
> If xfs_repair cannot fix it, you will have to look out a version that
> contains some fixes related to handling this kind of corruption:
>
> http://oss.sgi.com/archives/xfs/2006-07/msg00374.html
Martin,
thanks for your help. I did use both 2.6.17.1 and 2.6.17.3 before
2.6.17.9... So I guess (hope) that's the problem, and not my memory...
I have run xfs_repair 2.8.11 on two filesystems with errors (luckily,
neither my /home nor my backup partition seems to be hit), and it find
some errors, but if I run it again, I finds the same errors over and
over again... I seem to have it up and running again now, but I really
don't like that xfs_repair shows a lot of errors on each run. Don't like
that at all... It says it has fixed the errors, but I just never get rid
of them.
Is that normal? Guess not. And is it something that can happen with the
directory corruption bug? I read that I needed to have xfsprogs >2.8.10,
but that didn't help neither...
Best regards,
Stian
next prev parent reply other threads:[~2006-08-25 1:00 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-08-24 9:45 xfs bug in 2.6.17.9? Stian Jordet
2006-08-24 12:29 ` Martin Steigerwald
2006-08-24 23:45 ` Stian Jordet [this message]
2006-08-24 13:42 ` Justin Piszcz
2006-08-24 23:47 ` Stian Jordet
2006-08-25 1:58 ` Nathan Scott
2006-08-25 6:15 ` Stian Jordet
2006-08-25 8:38 ` Stian Jordet
2006-08-25 5:08 ` Chris Wedgwood
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=1156463133.19666.4.camel@localhost.localdomain \
--to=liste@jordet.net \
--cc=Martin@lichtvoll.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