public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Ed Sweetman <ed.sweetman@wmich.edu>
To: linux-kernel@vger.kernel.org
Subject: ext3 fs problem in 2.4.18-rc1?
Date: 17 Feb 2002 03:08:04 -0500	[thread overview]
Message-ID: <1013933289.18783.8.camel@psuedomode> (raw)

I'm using 2.4.18-rc1 with the preempt patch and whenever I run fsck, it
keeps finding more and more errors.  Specifically those related to
corrupted orphan linked lists. I dont know what is going on but I know
it's not the drives because they were all tested before partitioning
under an older (woody's kernel) and everything was fine (bad block
test).  

No matter how many times I run fsck, even immediately after a previous
run, it picks up the same errors along with new ones it seemingly
created in the last run. 

if there is any more information about the problem I can give just say
what's needed. I'd like to get to the bottom of this. 


             reply	other threads:[~2002-02-17  8:08 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-02-17  8:08 Ed Sweetman [this message]
2002-02-19 10:55 ` ext3 fs problem in 2.4.18-rc1? Matthias Andree

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=1013933289.18783.8.camel@psuedomode \
    --to=ed.sweetman@wmich.edu \
    --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