From: "Gabor Z. Papp" <gzp@myhost.mynet>
To: linux-kernel@vger.kernel.org
Subject: Linux 2.4.19-rc3-ac3 and ext3 problems
Date: Mon, 29 Jul 2002 14:37:06 +0200 [thread overview]
Message-ID: <20020729123706.GC463@gzp2.gzp.hu> (raw)
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.
next reply other threads:[~2002-07-29 12:33 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20020729123706.GC463@gzp2.myhost.mynet>
2002-07-29 12:37 ` Gabor Z. Papp [this message]
2002-07-29 13:59 ` Alan Cox
2002-07-29 13:12 ` Gabor Z. Papp
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20020729123706.GC463@gzp2.gzp.hu \
--to=gzp@myhost.mynet \
--cc=linux-kernel@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®