From: Andreas Dilger <adilger@turbolinux.com>
To: "Fr�d�ric L. W. Meunier" <0@pervalidus.net>
Cc: Linux Kernel <linux-kernel@vger.kernel.org>
Subject: Re: EXT2-fs error with 2.4.4 (using CVS)
Date: Mon, 7 May 2001 22:45:59 -0600 (MDT) [thread overview]
Message-ID: <200105080445.f484jxL6000663@webber.adilger.int> (raw)
In-Reply-To: <20010508011610.P15636@pervalidus> from Fr�d�ric L. W. Meunier at May 8, 2001 01:16:10 am
Federic Meunier writes:
> ==> /var/log/syslog <==
> May 8 00:25:52 pervalidus kernel: EXT2-fs error (device ide0(3,3)): ext2_readdir: bad entry in
> directory #162813: directory entry across blocks - offset=92, inode=451111, rec_len=16404,
> name_len=9
> May 8 00:25:52 pervalidus kernel: EXT2-fs error (device ide0(3,3)): ext2_readdir: bad entry in
> directory #162813: directory entry across blocks - offset=92, inode=451111, rec_len=16404,
> name_len=9
>
> When CVS finished, I received the following error:
>
> May 8 01:11:29 pervalidus kernel: EXT2-fs error (device ide0(3,3)): ext2_readdir: bad entry in
> directory #162813: directory entry across blocks - offset=92, inode=451111, rec_len=16404,
> name_len=9
> May 8 01:11:29 pervalidus kernel: EXT2-fs error (device ide0(3,3)): ext2_readdir: bad entry in
> directory #162813: directory entry across blocks - offset=92, inode=451111, rec_len=16404,
> name_len=9
Since it is always the same inode, I would say it is corrupt. You need to
run e2fsck to fix it. It looks like it is a single-bit error on the disk.
The rec_len=16404=0x4014. One (of many possible) valid rec_len would be
0x14=20. To be valid we need name_len <= rec_len <= block size.
Chances are, when you run e2fsck, it will fix this dirent, but the rest of
the directory entries in that block will be moved to lost+found.
I would suspect a hardware problem, to create a single-bit error (if it
is such).
Cheers, Andreas
--
Andreas Dilger \ "If a man ate a pound of pasta and a pound of antipasto,
\ would they cancel out, leaving him still hungry?"
http://www-mddsp.enel.ucalgary.ca/People/adilger/ -- Dogbert
next prev parent reply other threads:[~2001-05-08 4:46 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-05-08 4:16 EXT2-fs error with 2.4.4 (using CVS) Frédéric L. W. Meunier
2001-05-08 4:45 ` Andreas Dilger [this message]
2001-05-08 5:13 ` Frédéric L. W. Meunier
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=200105080445.f484jxL6000663@webber.adilger.int \
--to=adilger@turbolinux.com \
--cc=0@pervalidus.net \
--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