| To: | Kasper Sandberg <lkml@xxxxxxxxxxx>, Justin Piszcz <jpiszcz@xxxxxxxxxxxxxxx>, Torsten Landschoff <torsten@xxxxxxxxxx> |
|---|---|
| Subject: | FAQ updated (was Re: XFS breakage...) |
| From: | Nathan Scott <nathans@xxxxxxx> |
| Date: | Thu, 20 Jul 2006 17:13:10 +1000 |
| Cc: | linux-kernel@xxxxxxxxxxxxxxx, xfs@xxxxxxxxxxx |
| In-reply-to: | <1153304468.3706.4.camel@localhost>; from lkml@xxxxxxxxxxx on Wed, Jul 19, 2006 at 12:21:08PM +0200 |
| References: | <20060718222941.GA3801@xxxxxxxxxxxxxxx> <20060719085731.C1935136@xxxxxxxxxxxxxxxxxxxxxxxx> <1153304468.3706.4.camel@localhost> |
| Sender: | xfs-bounce@xxxxxxxxxxx |
| User-agent: | Mutt/1.2.5i |
On Wed, Jul 19, 2006 at 12:21:08PM +0200, Kasper Sandberg wrote:
> On Wed, 2006-07-19 at 08:57 +1000, Nathan Scott wrote:
> > On Wed, Jul 19, 2006 at 12:29:41AM +0200, Torsten Landschoff wrote:
> > >
> > > Jul 17 07:33:53 pulsar kernel: xfs_da_do_buf: bno 16777216
> > > Jul 17 07:33:53 pulsar kernel: dir: inode 54526538
> >
> > I suspect you had some residual directory corruption from using the
> > 2.6.17 XFS (which is known to have a lurking dir2 corruption issue,
> > fixed in the latest -stable point release).
Correction there - no -stable exists with this yet, I guess that'll
be 2.6.17.7 once its out though.
> what action do you suggest i do now?
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.
cheers.
--
Nathan
|
| Previous by Date: | Re: stable xfs, Chris Wedgwood |
|---|---|
| Next by Date: | TAKE 907752 - faq.html, Nathan Scott |
| Previous by Thread: | Re: XFS breakage in 2.6.18-rc1, Nathan Scott |
| Next by Thread: | Re: FAQ updated (was Re: XFS breakage...), Martin Steigerwald |
| Indexes: | [Date] [Thread] [Top] [All Lists] |