public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Scott Henson <shenson2@silvercoin.dyndns.org>
To: linux-kernel@vger.kernel.org
Subject: Re: harddisk corruption with 2.5.41bk and tcq enabled
Date: 13 Oct 2002 19:30:22 -0400	[thread overview]
Message-ID: <1034551822.10428.7.camel@GreyGhost> (raw)
In-Reply-To: <1034422647.3da8097797dd3@smartmail.portrix.net>

On Sat, 2002-10-12 at 07:37, Jan Dittmer wrote:
> > > attempt to access beyond end of device
> > > ide0(3,2): rw=0, want=1076371720, limit=19535040
> >
> At least not ide related. Just ext3 moaning.
> I'm just reinstalling debian, e2fsck just killed most of my filesystem :-(
> (including old dmesg/config).
> I'll give 2.4.42 a try on a fresh install with ext_2_. But I think there
> were no changes with respect to ext3 lately?!
> 

I had similar problems with 2.4.20-pre5-ac6 where my /home partition was
totally killed.  Though I used 2.4.19 to dd it off and ran fsck on
copies till I got it back and remounted it as a ext2 partition.  It had
some really bad corruption in the journal, but as far as I could tell
there was no other corruption.  I originally thought it was bad hard
disk, but I reinstalled to the same drive and no more errors with
2.4.20-pre8-ac3.  I also got all kinds off errors about trying to read
past the end of the device and partition magic said something about the
partition table being corrupt and not being able to determine the
partition type. Though cfdisk didnt say a thing about any of this.  Just
a wierd situation that had me confused for several days.  
-Scott Henson


  reply	other threads:[~2002-10-13 23:26 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-10-12  8:50 harddisk corruption with 2.5.41bk and tcq enabled Jan Dittmer
2002-10-12  9:06 ` David S. Miller
2002-10-12  9:16 ` Jens Axboe
2002-10-12 11:37   ` Jan Dittmer
2002-10-13 23:30     ` Scott Henson [this message]
2002-10-12 18:40   ` Jan Dittmer

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=1034551822.10428.7.camel@GreyGhost \
    --to=shenson2@silvercoin.dyndns.org \
    --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