xfs
[Top] [All Lists]

Re: corruption bug in 2.6.17

To: "Raz Ben-Jehuda(caro)" <raziebe@xxxxxxxxx>
Subject: Re: corruption bug in 2.6.17
From: Christian Kujau <lists@xxxxxxxxxxxxxxx>
Date: Tue, 5 Jun 2007 22:24:32 +0200 (CEST)
Cc: xfs@xxxxxxxxxxx
In-reply-to: <5d96567b0706050127y7f5eap7b92cddb5cdae02d@xxxxxxxxxxxxxx>
References: <5d96567b0706021407q4455b60asd9d23ef82cb90b55@xxxxxxxxxxxxxx> <alpine.DEB.0.99.0706022300140.16496@xxxxxxxxxxxxxxxxxx> <5d96567b0706050127y7f5eap7b92cddb5cdae02d@xxxxxxxxxxxxxx>
Sender: xfs-bounce@xxxxxxxxxxx

[please reply on-list, so that everbody can help. and top-posting is
 evil;) ]

On Tue, 5 Jun 2007, Raz Ben-Jehuda(caro) wrote:
It is unclear from the web page how can reproduce this bug. Can you
think of a several steps that produces it so I will be able to know
whether 2.7.17.7 fix had fixed it ?

I have been bitten by this one too and to "reproduce" it I only had to

 1) boot 2.6.17.x (x<17)
 2) generate some IO on the xfs-mounted partition...and wait until the
    fs shut down.

The fix is really to use a 2.7.17.7 or later kernel and check your
xfs with xfsprogs (version 2.8.10 or later) - if no corruptions are found, you should be fine.

C.
--
make bzImage, not war


<Prev in Thread] Current Thread [Next in Thread>