From: David Greaves <david@dgreaves.com>
To: linux-raid@vger.kernel.org
Subject: Serious XFS bug in 2.6.17 kernels - FYI
Date: Thu, 20 Jul 2006 21:07:07 +0100 [thread overview]
Message-ID: <44BFE26B.4060703@dgreaves.com> (raw)
Just an FYI for my friends here who may be running 2.6.17.x kernels and
using XFS and who may not be monitoring lkml :)
There is a fairly serious corruption problem that has recently been
discussed on lkml and affects all 2.6.17 before -stable .7 (not yet
released)
Essentially the fs can be corrupted and it's serious because the current
xfs_repair tools may make the problem worse, not better.
There is a 1-line patch that can be applied :
http://marc.theaimsgroup.com/?l=linux-kernel&m=115315508506996&w=2
FAQ message here
http://marc.theaimsgroup.com/?l=linux-xfs&m=115338022506482&w=2
FAQ:
http://oss.sgi.com/projects/xfs/faq.html#dir2
It appears that efforts are being focused on the repair tools now.
It appears to me that the best response is to patch the kernel, reboot,
backup the fs, recreate the fs and restore - but please read up before
taking any action.
David
--
reply other threads:[~2006-07-20 20:07 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=44BFE26B.4060703@dgreaves.com \
--to=david@dgreaves.com \
--cc=linux-raid@vger.kernel.org \
/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;
as well as URLs for NNTP newsgroup(s).