more error messages are present: it's just a small selection...
Dec 30 15:17:34 jaguar kernel: hda: write_intr error1: nr_sectors=1,
stat=0x70
Dec 30 15:17:34 jaguar kernel: hda: write_intr: status=0x70 { DriveReady
DeviceFault SeekComplete }
Dec 30 15:37:58 jaguar kernel: hda: write_intr error1: nr_sectors=188,
stat=0x78
Dec 31 17:00:40 jaguar kernel: hda: status error: status=0x58 { DriveReady SeekComplete DataRequest }
Dec 31 17:00:40 jaguar kernel: hda: drive not ready for command
Dec 31 17:00:40 jaguar kernel: hda: status error: status=0x58 { DriveReady
SeekComplete DataRequest }
Dec 31 17:00:40 jaguar kernel: hda: drive not ready for command
Thanksm
Matt
On Mon, 7 Jan 2002, Stephen C. Tweedie wrote:
> Hi,
>
> On Sun, Jan 06, 2002 at 10:43:27PM +0000, Matthew Dickinson wrote:
>
> > RedHat 7.2, ext3 on /, kernel 2.4.18p1.
> >
> > whilst updatedb was running, i had these messages appear...
> >
> > Jan 6 22:18:42 jaguar kernel: EXT3-fs error (device ide0(3,3)):
> > ext3_readdir: bad entry in directory #147553: rec_len %% 4 != 0 -
> > offset=0, inode=1651076143, rec_len=19527, name_len=85
> > Jan 6 22:18:42 jaguar kernel: EXT3-fs error (device ide0(3,3)):
> > ext3_readdir: bad entry in directory #50619: rec_len is too small for
> > name_len - offset=0, inode=574907, rec_len=12, name_len=9
> > Jan 6 22:18:43 jaguar kernel: EXT3-fs error (device ide0(3,3)):
> > ext3_readdir: bad entry in directory #341627: rec_len is too small for
> > name_len - offset=0, inode=865915, rec_len=12, name_len=9
> >
> > i'm suspicious i have a hard disk error (it's a new laptop that's less
> > than a month old) and i wouldn't mind proof!
>
> Quite possibly. I'd do a forced fsck and see if the disk really has
> errors, or if it's simply a read error. Are there any other sorts of
> errors in the logs?
>
> Cheers,
> Stephen
>
>
>
> _______________________________________________
>
> Ext3-users@redhat.com
> https://listman.redhat.com/mailman/listinfo/ext3-users
>
