From: "Frédéric L. W. Meunier" <0@pervalidus.net>
To: Linux Kernel <linux-kernel@vger.kernel.org>
Subject: Re: EXT2-fs error with 2.4.4 (using CVS)
Date: Tue, 8 May 2001 02:13:44 -0300 [thread overview]
Message-ID: <20010508021344.Q15636@pervalidus> (raw)
In-Reply-To: <200105080445.f484jxL6000663@webber.adilger.int>
On Mon, May 07, 2001 at 10:45:59PM -0600, Andreas Dilger wrote:
<skip>
> > 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.
OK, I ran.
# fsck -v /dev/ide/host0/bus0/target0/lun0/part3
Parallelizing fsck version 1.19 (13-Jul-2000)
e2fsck 1.19, 13-Jul-2000 for EXT2 FS 0.5b, 95/08/09
/dev/ide/host0/bus0/target0/lun0/part3 contains a file system with errors, check forced.
Pass 1: Checking inodes, blocks, and sizes
Pass 2: Checking directory structure
Pass 3: Checking directory connectivity
Pass 4: Checking reference counts
Pass 5: Checking group summary information
159689 inodes used (31%)
1363 non-contiguous inodes (0.9%)
# of inodes with ind/dind/tind blocks: 3884/1/0
408910 blocks used (79%)
0 bad blocks
145848 regular files
13624 directories
0 character device files
0 block device files
0 fifos
2 links
208 symbolic links (208 fast symbolic links)
0 sockets
--------
159682 file
> 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.
Nothing in /usr/local/src/lost+found
> I would suspect a hardware problem, to create a single-bit error (if it
> is such).
I hope not. I know at least my RAM is OK. I installed 256Mb
before booting with 2.4.4 and tested all with memtest86.
CVS couldn't remove mozilla/xpinstall/wizard/windows/nszip
after the process terminated, but
mozilla/xpinstall/wizard/windows/nszip/Entries and
mozilla/xpinstall/wizard/windows/nszip/Tag were updated after
the first EXT2-fs error messages.
Well, everything seems OK for now. Thanks.
--
0@pervalidus.{net, {dyndns.}org} Tel: 55-21-717-2399 (Niterói-RJ BR)
prev parent reply other threads:[~2001-05-08 5:13 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
2001-05-08 5:13 ` Frédéric L. W. Meunier [this message]
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=20010508021344.Q15636@pervalidus \
--to=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