| To: | Stian Jordet <liste@xxxxxxxxxx> |
|---|---|
| Subject: | Re: xfs bug in 2.6.17.9? |
| From: | Nathan Scott <nathans@xxxxxxx> |
| Date: | Fri, 25 Aug 2006 11:58:58 +1000 |
| Cc: | Justin Piszcz <jpiszcz@xxxxxxxxxxxxxxx>, xfs@xxxxxxxxxxx |
| In-reply-to: | <1156463263.19666.7.camel@xxxxxxxxxxxxxxxxxxxxx>; from liste@xxxxxxxxxx on Fri, Aug 25, 2006 at 01:47:43AM +0200 |
| References: | <92b7ea0a0608240245v700f19dex6ecb688efcab657b@xxxxxxxxxxxxxx> <Pine.LNX.4.64.0608240942180.30908@xxxxxxxxxxxxxxxx> <1156463263.19666.7.camel@xxxxxxxxxxxxxxxxxxxxx> |
| Sender: | xfs-bounce@xxxxxxxxxxx |
| User-agent: | Mutt/1.2.5i |
On Fri, Aug 25, 2006 at 01:47:43AM +0200, Stian Jordet wrote: > tor, 24,.08.2006 kl. 09.42 -0400, skrev Justin Piszcz: > > Aug 24 09:22:09 buick kernel: xfs_da_do_buf: bno 16777216 > > > > That is the bug from 2.6.17 -> 2.6.17.6. > > > > It was patched in 2.6.17.7, but I assume(?) if you never fixed your FS to > > begin with, you will still have the problem. Read the XFS FAQ, and backup > > your data before you do that :) > > As I just wrote to Martin, I did run a couple of those kernels. But even > with updated xfsprogs I can't fix the errors... Is that "normal", or am > I in deep trouble? This is likely to be lost+found being recreated each time, its normal if you don't do something about the lost+found files - once those are renamed/removed, it should run cleanly. cheers. -- Nathan |
| <Prev in Thread] | Current Thread | [Next in Thread> |
|---|---|---|
| ||
| Previous by Date: | Re: xfs bug in 2.6.17.9?, Stian Jordet |
|---|---|
| Next by Date: | [PATCH] collapse sv_init, init_sv on linux, sandeen |
| Previous by Thread: | Re: xfs bug in 2.6.17.9?, Stian Jordet |
| Next by Thread: | Re: xfs bug in 2.6.17.9?, Stian Jordet |
| Indexes: | [Date] [Thread] [Top] [All Lists] |