On Thu, Dec 14, 2006 at 06:21:49PM +0900, Shinichiro HIDA wrote:
> Hi,
>
> ;; Sorry for late, and Thanks for following up.
>
> >>>>> In <[email protected]>
> >>>>> David Chinner <[email protected]> wrote:
> > On Wed, Dec 13, 2006 at 02:12:23PM +0900, Shinichiro HIDA wrote:
> > > Hi,
> > >
> > > I met same problem on my 2 machines, 2.6.19 (Debian unstable) also
> > > 2.6.18.3 (Debian stable),
> > Should have been preceeded with some other output explaining the
> > reason for the shutdown.
> Dec 12 21:31:25 lune kernel: xfs_da_do_buf: bno 16777216
> Dec 12 21:31:25 lune kernel: dir: inode 9078346
> Dec 12 21:31:25 lune kernel: Filesystem "hdf5": XFS internal error xfs_da_do_buf(1) at line 1995 of file fs/xfs/xfs_da_btree.c. Caller 0xc02982ec
Ok, that bno (16777216) is a definite sign of corruption
caused by the 2.6.17.x (x <=6) kernels.
> > Did these machines run 2.6.17.x where x<= 6?
> > i.e. is this problem:
>
> > http://oss.sgi.com/projects/xfs/faq.html#dir2
>
> Yes, I could boot this machine(lune) with 2.6.17.6.
I wasn't suggesting that you use this kernel - that could cause more
corruption to occur. What I was asking is if you have run a kernel
of this version in the past (i.e. before you upgraded to 2.6.18.3)?
Regardless, I suggest you get the latest xfsprogs and run xfs_repair
on your filesystems to fix the problem.
Cheers,
Dave.
--
Dave Chinner
Principal Engineer
SGI Australian Software Group
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [email protected]
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
[Index of Archives]
[Kernel Newbies]
[Netfilter]
[Bugtraq]
[Photo]
[Stuff]
[Gimp]
[Yosemite News]
[MIPS Linux]
[ARM Linux]
[Linux Security]
[Linux RAID]
[Video 4 Linux]
[Linux for the blind]
[Linux Resources]
