Linux 2.4.19-rc3-ac3 and ext3 problems

[Alan Cox]

On Mon, 2002-07-29 at 13:37, Gabor Z. Papp wrote:
> Extreme usage of a IC35L060AVVA07-0 ATA DISK drive,
> 120103200 sectors (61493 MB) w/1863KiB Cache, CHS=119150/16/63, UDMA(100)
> on a PDC20268: (U)DMA Burst Bit ENABLED Primary MASTER Mode
> Secondary MASTER Mode controller ends up with:

Thanks. If you try the same with the base 2.4.19-rc3 can you duplicate
the problem or not ?

-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majo...@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/

[Gabor Z. Papp]

Extreme usage of a IC35L060AVVA07-0 ATA DISK drive,
120103200 sectors (61493 MB) w/1863KiB Cache, CHS=119150/16/63, UDMA(100)
on a PDC20268: (U)DMA Burst Bit ENABLED Primary MASTER Mode
Secondary MASTER Mode controller ends up with:

EXT3-fs error (device ide2(33,1)): ext3_readdir: bad entry in directory #4325599: directory entry across blocks - offset=0, inode=4082854266, rec_len=55184, name_len=162
Aborting journal on device ide2(33,1).
Remounting filesystem read-only
EXT3-fs error (device ide2(33,1)): ext3_readdir: bad entry in directory #4391169: rec_len % 4 != 0 - offset=0, inode=2583923720, rec_len=30815, name_len=118
EXT3-fs error (device ide2(33,1)): ext3_readdir: bad entry in directory #5914810: rec_len % 4 != 0 - offset=0, inode=3706019706, rec_len=39806, name_len=198
EXT3-fs error (device ide2(33,1)) in start_transaction: Journal has aborted
EXT3-fs error (device ide2(33,1)): ext3_readdir: bad entry in directory #6553840: directory entry across blocks - offset=0, inode=501681528, rec_len=34100, name_len=165
EXT3-fs error (device ide2(33,1)): ext3_readdir: bad entry in directory #6537472: rec_len % 4 != 0 - offset=0, inode=3987959021, rec_len=25889, name_len=144
EXT3-fs error (device ide2(33,1)): ext3_readdir: bad entry in directory #4325597: rec_len % 4 != 0 - offset=0, inode=2071797251, rec_len=48853, name_len=133
EXT3-fs error (device ide2(33,1)): ext3_readdir: bad entry in directory #5701833: inode out of bounds - offset=0, inode=11406299, rec_len=3036, name_len=174
EXT3-fs error (device ide2(33,1)): ext3_readdir: bad entry in directory #4391167: rec_len % 4 != 0 - offset=0, inode=2583923720, rec_len=30815, name_len=118
EXT3-fs error (device ide2(33,1)): ext3_readdir: bad entry in directory #6324474: rec_len % 4 != 0 - offset=0, inode=1687223295, rec_len=207, name_len=3
EXT3-fs error (device ide2(33,1)): ext3_readdir: bad entry in directory #6553838: directory entry across blocks - offset=0, inode=3580267195, rec_len=59804, name_len=52
EXT3-fs error (device ide2(33,1)): ext3_readdir: bad entry in directory #4620448: rec_len % 4 != 0 - offset=0, inode=1646798880, rec_len=26229, name_len=102
EXT3-fs error (device ide2(33,1)): ext3_readdir: bad entry in directory #4767991: rec_len is smaller than minimal - offset=0, inode=3963995904, rec_len=0, name_len=0
EXT3-fs error (device ide2(33,1)): ext3_readdir: bad entry in directory #4767992: rec_len % 4 != 0 - offset=0, inode=39302671, rec_len=35666, name_len=69

Same heavy usage (untargzipping several tarballs in total
size of over 2GB) on 2.4.18 show up no error.

[Gabor Z. Papp]

* Alan Cox <al...@lxorguk.ukuu.org.uk>:

|> Extreme usage of a IC35L060AVVA07-0 ATA DISK drive,
|> 120103200 sectors (61493 MB) w/1863KiB Cache, CHS=119150/16/63, UDMA(100)
|> on a PDC20268: (U)DMA Burst Bit ENABLED Primary MASTER Mode
|> Secondary MASTER Mode controller ends up with:
|

| Thanks. If you try the same with the base 2.4.19-rc3 can you duplicate
| the problem or not ?

No, seems like I can't.