All of lore.kernel.org
 help / color / mirror / Atom feed
From: CaT <cat@zip.com.au>
To: "Stephen C. Tweedie" <sct@redhat.com>
Cc: linux-kernel <linux-kernel@vger.kernel.org>,
	Andrew Morton <akpm@digeo.com>,
	Andreas Dilger <adilger@clusterfs.com>
Subject: Re: ext3 error with 2.6.9-rc4
Date: Sat, 30 Oct 2004 13:52:31 +1000	[thread overview]
Message-ID: <20041030035231.GB1287@zip.com.au> (raw)
In-Reply-To: <1097772670.2120.57.camel@sisko.scot.redhat.com>

On Thu, Oct 14, 2004 at 05:51:10PM +0100, Stephen C. Tweedie wrote:
> > Oct 13 00:17:03 nessie kernel: EXT3-fs error (device hdh1): ext3_readdir: bad entry in directory #3522561: rec_len is smaller than minimal - offset=4084, inode=3523431, rec_len=0, name_len=0
> 
> All this really tells us is that there's something bogus on disk, not
> how it got there.  
> 
> There are tools like "dt" which may help identify whether there's data
> going bad on the way to disk, or whether it might be a fs fault.
> 
> http://www.bit-net.com/~rmiller/dt.html

Thanks for that. A new utlitity to learn. :) Anyways, after getting my
laptop (and hence my access to email) back after a week I did a fair bit
of testing and the only way I can duplicate the above is by copying from
one hd to another. Further testing has led me to believe that the ext3
error is more of a symptom of data corruption caused in the IDE layer
somewhere rather then anything else.

I've posted a bug wrt to what I've discovered in the ide update thread
(my message before this one).

-- 
    Red herrings strewn hither and yon.

  reply	other threads:[~2004-10-30  3:53 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-10-12 14:29 ext3 error with 2.6.9-rc4 CaT
2004-10-14 16:51 ` Stephen C. Tweedie
2004-10-30  3:52   ` CaT [this message]
     [not found] <fa.cbe1dra.16ke3gi@ifi.uio.no>
2004-10-14  4:12 ` Robert Hancock

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=20041030035231.GB1287@zip.com.au \
    --to=cat@zip.com.au \
    --cc=adilger@clusterfs.com \
    --cc=akpm@digeo.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=sct@redhat.com \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.