From: Andreas Dilger <adilger@clusterfs.com>
To: Ed Sweetman <safemode@speakeasy.net>
Cc: linux-kernel@vger.kernel.org
Subject: Re: non-critical ext3-fs errors?
Date: Tue, 23 Jul 2002 14:48:33 -0600 [thread overview]
Message-ID: <20020723204833.GR25899@clusterfs.com> (raw)
In-Reply-To: <1027456090.1982.28.camel@psuedomode>
On Jul 23, 2002 16:28 -0400, Ed Sweetman wrote:
> I notice these errors every now and then on my 100GB WD drive
> (partitioned into bits) and particularly on this partition that I
> compile everything on.
>
> EXT3-fs error (device ide0(3,7)): ext3_readdir: bad entry in directory
> #17821: directory entry across blocks - offset=24, inode=17822,
> rec_len=4076, name_len=3
This is definitely a bad entry - offset + rec_len (4100) != blocksize (4096).
Strange. You need to run e2fsck -f on this partition. It sounds like
you are getting some corruption or bit flips happening.
> Now these errors dont cause the system to panic like other ext3 errors
> do, so i'm wondering what the significance of these errors are.
Well, this is an error, and the next time the computer is restarted it
should force a full fsck on the partition. The other "panic" (oops)
situations are when things are totally shot and it is better to stop
doing anything than try and continue. In this case, it is possible to
continue, but that doesn't mean things are OK.
Cheers, Andreas
--
Andreas Dilger
http://www-mddsp.enel.ucalgary.ca/People/adilger/
http://sourceforge.net/projects/ext2resize/
next prev parent reply other threads:[~2002-07-23 20:47 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-07-23 20:28 non-critical ext3-fs errors? Ed Sweetman
2002-07-23 20:48 ` Andreas Dilger [this message]
2002-07-24 0:19 ` non-critical ext3-fs errors and IDE issues with 2.4.19-rc3 Ed Sweetman
2002-07-24 23:01 ` Andreas Dilger
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=20020723204833.GR25899@clusterfs.com \
--to=adilger@clusterfs.com \
--cc=linux-kernel@vger.kernel.org \
--cc=safemode@speakeasy.net \
/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