From: mkloppstech@freenet.de
To: linux-kernel@vger.kernel.org
Subject: Ext2-fs error
Date: Wed, 6 Dec 2000 22:50:43 +0100 (CET) [thread overview]
Message-ID: <200012062150.WAA01033@john.epistle> (raw)
The EXT2-fs errors I recently reported for test11 seem to be gone with
test12-pre5. At least I couldn't reproduce the error, neither with
overcommit_memory turned on nor off; maybe the error was due to
turning on write cache of my hard disk.
The error was a wrong reading of directory lengths and inode nnumbers:
The file system seemed to read the inode numbers not as supposed to do:
xxxx|xxxx|xxxx|xxxx|xxxx
rrrr
but like this:
xxxx|xxxx|xxxx|xxxx|xxxx
rrr_r
The message was:
Dec 4 13:04:19 john kernel: EXT2-fs error (device ide0(3,3)): ext2_readdir: bad entry in directory #280596: rec_len % 4 != 0 - offset=0, inode=68583844, rec_len=13758, name_len=0
Dec 4 15:38:07 john kernel: EXT2-fs error (device ide0(3,3)): ext2_readdir: bad entry in directory #280596: rec_len % 4 != 0 - offset=0, inode=33188, rec_len=3591, name_len=0
Dec 4 15:38:07 john kernel: EXT2-fs error (device ide0(3,3)): ext2_readdir: bad entry in directory #659481: directory entry across
blocks - offset=0, inode=33188, rec_len=2536, name_len=0
Dec 4 15:39:38 john kernel: EXT2-fs error (device ide0(3,3)): ext2_readdir: bad entry in directory #280596: rec_len % 4 != 0 - offset=0, inode=33188, rec_len=3591, name_len=0
Dec 4 15:39:38 john kernel: EXT2-fs error (device ide0(3,3)): ext2_readdir: bad entry in directory #659481: directory entry across
blocks - offset=0, inode=33188, rec_len=2536, name_len=0
Mirko Kloppstech
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
Please read the FAQ at http://www.tux.org/lkml/
next reply other threads:[~2000-12-06 22:21 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-12-06 21:50 mkloppstech [this message]
-- strict thread matches above, loose matches on Subject: below --
2001-02-22 7:02 EXT2-fs error Mohammad A. Haque
2001-02-22 8:10 ` Andreas Dilger
2001-02-22 14:58 ` Mohammad A. Haque
2001-02-23 19:12 Ian Wehrman
2001-02-23 11:46 ` John Heil
2001-02-23 19:26 ` Alan Cox
2001-02-23 11:50 ` John Heil
2001-02-24 11:02 ` A E Lawrence
2001-02-24 16:59 ` Alan Cox
2001-02-24 22:30 ` A E Lawrence
2001-02-24 23:08 ` A E Lawrence
2001-02-25 20:52 ` A E Lawrence
2001-02-25 13:53 ` John Heil
2001-02-25 17:58 ` Mike Brown
2001-03-30 3:06 khromy
2001-03-30 6:57 ` Rogier Wolff
2001-04-02 23:13 ` Alan Cox
2001-03-30 13:49 ` Dale E Martin
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=200012062150.WAA01033@john.epistle \
--to=mkloppstech@freenet.de \
--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