Mailing List Archive

Re: I *need* to know what this is.
Kurt Hockenbury wrote:
>
> On Tue, 19 Jan 1999, Jeremy Hansen wrote:
>
> > EXT2-fs error (device 08:01): ext2_find_entry: bad entry in directory
> > #284673: rec_len is too small for name_len - offset=1436, inode=284754,
> > rec_len=20, name_len=41
> >
> > We have burned three machines now and all three are getting the same
> > error. I need to have an idea what this is. I find it hard to
> > believe that we happen to get three bad drives in a row. All hardware
> > has been switched out at least three times.
> >
> > I need an *answer* on this.
Strange. This is a scsi drive, so I don't believe hdparm works with
scsi.
Is there something similar with scsi drives? I though DMA was an ide
thing,
but I'm probable wrong.
Thanks
-jeremy

> I was getting ext2-fs errors on one of our machines until I did the
> following in startup rc:
>
> /sbin/hdparm -d 0 /dev/hda # Turn off dma, see if that stops the filesystem
> # bit errors.
>
> Seems (knock wood) to have fixed it here.
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.rutgers.edu
Please read the FAQ at http://www.tux.org/lkml/
Re: I *need* to know what this is. [ In reply to ]
Ok, first, if I told you I've used three different drives and got
the same error, how would it matter what the current hd specs are?
kernel is a stock 2.0.35 kernel from rh 5.1.
I'm assuming this error MEANS something and isn't reliant on
a specific manufacturer, but to satisfy everyone who may be
asking the same questions:
brand is a 6.4gig Quantum Fireball SE.
The interface is scsi, but it's happened on many ide drives as well.
The other drives were Quantums as well. If there is a problem with
quantum drives and linux, that would be swell, but I need to know.
Thanks
-jeremy
dtillman@cannonexpress.com wrote:
>
> > EXT2-fs error (device 08:01): ext2_find_entry: bad entry in directory
> > #284673: rec_len is too small for name_len - offset=1436, inode=284754,
> > rec_len=20, name_len=41
> >
> > We have burned three machines now and all three are getting the same
> > error. I need to have an idea what this is. I find it hard to
> > believe that we happen to get three bad drives in a row. All hardware
> > has been switched out at least three times.
> >
> > I need an *answer* on this.
>
> Not intending to rant, but this sort of thing drives me nuts.
>
> What kernel version?
>
> What HD size?
>
> What HD brand?
>
> What HD interface?
>
> No one one the list is psychic, just psycho...
>
> If you are using UDM drives, and pre 2.0.34 kernels, you may
> experience unhappiness.
>
> -Dave
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.rutgers.edu
Please read the FAQ at http://www.tux.org/lkml/
Re: I *need* to know what this is. [ In reply to ]
On Tue, 19 Jan 1999, Jeremy Hansen wrote:
> Strange. This is a scsi drive, so I don't believe hdparm works with
> scsi.
> Is there something similar with scsi drives? I though DMA was an ide
> thing,
> but I'm probable wrong.
I didn't realize this was a SCSI drive. In that case, your most likely
problem is bad cabling or bad termination. Try using a different cable,
and active termination.
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.rutgers.edu
Please read the FAQ at http://www.tux.org/lkml/