Hello!
I hope that fixed it, there quite a few errors..
However i find it weird that on another partition which is double in size and
almost all the time writes or reads something, didn't have any errors...
Also couldn't there be implemented instead of a kernel error a message or
something ?
Radu
On Tuesday 26 August 2003 20:10, you wrote:
> On Tue, 2003-08-26 at 11:43, Axel Thimm wrote:
> > Hi,
> >
> > I got a bug report by radus using the atrpms kernels on Debian (the
> > kernels are for RedHat and he takes the kernel-source rpm and uses it
> > for building on Debian with some workarounds for gcc 3.3).
> >
> > The kernel in question has
> > o Red Hat 2.4.20-20.9 base sources
> > o XFS 1.3.0 merged in
> > o Updated lvm to 1.0.7
> >
> > also some further patches that should not overlap with XFS:
> >
> > o i2c/lm_sensors 2.8.0
> > o v4l2 api
> > o 3ware driver updates.
> >
> > Here is the user's oops:
> > > Aug 26 06:25:14 stark kernel: Filesystem "ide0(3,2)": XFS internal
> > > error xfs_iformat(6) at line 544 of file xfs_inode.c. Caller
> > > 0xc01b8472 Aug 26 06:25:14 stark kernel: c09dfd0c c01b6f11 c02d37d0
> > > 00000001 c1ad4c00 c02d3790 00000220 c01b8472
> > > Aug 26 06:25:14 stark kernel: c3c95a16 00000008 c1ad4c00
> > > 99a49e15 159e4e82 00000000 00000000 00000000
> > > Aug 26 06:25:14 stark kernel: 00000000 c1ad4c00 c671ac00
> > > c01b8472 c671ac00 c3c95a00 00000001 00000000
>
> That is a corrupt inode on the disk, time to break out xfs_repair. Do
> a quick mount and unmount of the fs first, then run xfs_check and save
> the output, finally run xfs_repair and send us the output of both
> commands.
>
> Steve
errors.txt
Description: Text document
repair1.txt
Description: Text document
|