Marc Dietrich wrote: > Hi, > > On Monday 25 February 2008 01:36:28 Barry Naujok wrote: >> On Sun, 24 Feb 2008 20:58:26 +1100, Marc Dietrich >> >> wrote: >>> Hi, >>> >>> somewhere after the release of 2.6.24 my xfs filesystem got corrupted. >>> Initialy I thought it was only related to the readdir bug. >>> (http://oss.sgi.com/archives/xfs/2008-02/msg00027.html) So I waited for >>> the fix to go into mainline. Yesterday I tried again, but got this error >>> during boot: >> [stack trace snipped] >> >>> I seems that the log is corrupted because I can't mount the filesystem >>> anymore (blocks while replaying). Mounting with norecovery option works. >>> I tried to repair the filesystem, but xfs_repair also hangs in "Phase 3 >>> - scan and clear agi unlinks lists". Before, Phase 2 reports some >>> "ir_freecount/free.mismatch" lines. >> Might have to add this to the FAQ as this is the second time someone has >> reported Phase 3 hanging. >> >> Try running xfs_repair -P to try and get past this problem if you are >> running xfsprogs 2.9.x. > > I tried this, but didn't work either and is also not my main problem. The > problem is, as the subject says, that every time I boot linux the filesystem > gets corrupted (and unrepairable). > > I will setup a testing partition, do some additional tests (could be a > miscompilation, I'm using gcc-4.3) and report back. > >>> This happens on a newly created filesystem with xfsprogs 2.6.9 (I also >>> tested 2.5.22). I have a 32bit powermac, so it could be an endian issue. > We've had a few problems reported with XFS on 32-bit powermacs and the culprit appears to be some changes to bit manipulation routines. Could you please try reverse applying the attached patches and see if the problem is resolved? Lachlan