| To: | Jan Kasprzak <kas@xxxxxxxxxx> |
|---|---|
| Subject: | Re: FAQ updated (was Re: XFS breakage...) |
| From: | Nathan Scott <nathans@xxxxxxx> |
| Date: | Wed, 2 Aug 2006 14:32:31 +1000 |
| Cc: | linux-kernel@xxxxxxxxxxxxxxx, xfs@xxxxxxxxxxx |
| In-reply-to: | <20060731162535.GA15555@xxxxxxxxxx>; from kas@xxxxxxxxxx on Mon, Jul 31, 2006 at 06:25:35PM +0200 |
| References: | <20060718222941.GA3801@xxxxxxxxxxxxxxx> <20060719085731.C1935136@xxxxxxxxxxxxxxxxxxxxxxxx> <1153304468.3706.4.camel@localhost> <20060720171310.B1970528@xxxxxxxxxxxxxxxxxxxxxxxx> <20060731162535.GA15555@xxxxxxxxxx> |
| Sender: | xfs-bounce@xxxxxxxxxxx |
| User-agent: | Mutt/1.2.5i |
On Mon, Jul 31, 2006 at 06:25:35PM +0200, Jan Kasprzak wrote: > Nathan Scott wrote: > : I've captured the state of this issue here, with options and ways > : to correct the problem: > : http://oss.sgi.com/projects/xfs/faq.html#dir2 > : > : Hope this helps. > > I have been hit with this bug as well - I tried to clear the > two corrupted directory inodes with xfs_db (as the FAQ entry says), then ran > xfs_repair (lots of files ended up in lost+found), but apparently > the volume is still not OK - when I tried to use it (this volume > is a public FTP archive), I got the following traces: There is now a fixed version of xfs_repair available - its in xfsprogs-2.8.10, source is on oss.sgi.com in the XFS ftp area. A number of people have reported success with Barry's earlier patch, noone's reported anything bad, so 2.8.10 is out now with the fix merged. cheers. -- Nathan |
| <Prev in Thread] | Current Thread | [Next in Thread> |
|---|---|---|
| ||
| Previous by Date: | TAKE 954405 -, Barry Naujok |
|---|---|
| Next by Date: | review: catch large memory allocations, Nathan Scott |
| Previous by Thread: | TAKE 954405 -, Barry Naujok |
| Next by Thread: | review: catch large memory allocations, Nathan Scott |
| Indexes: | [Date] [Thread] [Top] [All Lists] |