| To: | Christian Kujau <evil@xxxxxxxxxx> |
|---|---|
| Subject: | Re: XFS breakage in 2.6.18-rc1 |
| From: | Nathan Scott <nathans@xxxxxxx> |
| Date: | Sat, 29 Jul 2006 07:48:03 +1000 |
| Cc: | linux-kernel@xxxxxxxxxxxxxxx, xfs@xxxxxxxxxxx |
| In-reply-to: | <Pine.LNX.4.64.0607281526220.1882@sheep.housecafe.de>; from evil@g-house.de on Fri, Jul 28, 2006 at 05:01:24PM +0000 |
| References: | <20060718222941.GA3801@stargate.galaxy> <20060719085731.C1935136@wobbly.melbourne.sgi.com> <Pine.LNX.4.64.0607221722500.8407@prinz64.housecafe.de> <20060724090138.C2083275@wobbly.melbourne.sgi.com> <Pine.LNX.4.64.0607281526220.1882@sheep.housecafe.de> |
| Sender: | xfs-bounce@xxxxxxxxxxx |
| User-agent: | Mutt/1.2.5i |
On Fri, Jul 28, 2006 at 05:01:24PM +0000, Christian Kujau wrote: > I had two xfs filesystems and I first noticed that /data/Scratch was > befallen from this bug. I did not care much about this (hence the > name :)) and I wanted to postpone the xfs_db surgery. > ... > found more and more errors. I decided to mkfs the partition and make use > of my backups. my other "scratch" partition is still XFS but mounted ro > and I'll try the xfsprogs fixes Nathan published on this one. Barry sent an xfs_repair patch to resolve this issue to the xfs@xxxxxxxxxxx list yesterday; please give that a go and let us know how it fares. cheers. -- Nathan |
| <Prev in Thread] | Current Thread | [Next in Thread> |
|---|---|---|
| ||
| Previous by Date: | write back cache and barriers, calembour |
|---|---|
| Next by Date: | Re: question - xfs stress tests, Nathan Scott |
| Previous by Thread: | Re: XFS breakage in 2.6.18-rc1, Christian Kujau |
| Next by Thread: | Re: XFS breakage in 2.6.18-rc1, Ralf Hildebrandt |
| Indexes: | [Date] [Thread] [Top] [All Lists] |