public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: monkeyiq <monkeyiq@users.sourceforge.net>
To: Jens Axboe <axboe@suse.de>
Cc: Andi Kleen <ak@suse.de>, Andreas Dilger <adilger@turbolinux.com>,
	monkeyiq <monkeyiq@users.sourceforge.net>,
	linux-kernel@vger.kernel.org
Subject: Re: Dying disk and filesystem choice.
Date: 24 May 2001 22:08:30 +1000	[thread overview]
Message-ID: <m3eltfymo1.fsf@kloof.cr.au> (raw)
In-Reply-To: <m3bsoj2zsw.fsf@kloof.cr.au> <200105240658.f4O6wEWq031945@webber.adilger.int> <20010524103145.A9521@gruyere.muc.suse.de> <20010524121936.I12470@suse.de>
In-Reply-To: Jens Axboe's message of "Thu, 24 May 2001 12:19:36 +0200"

Jens Axboe <axboe@suse.de> writes:

> On Thu, May 24 2001, Andi Kleen wrote:
> > On Thu, May 24, 2001 at 12:58:14AM -0600, Andreas Dilger wrote:
> > > Well reiserfs is probably a very bad choice at this point.  It
> > > does not have any bad blocks support (yet), so as soon as you have
> > > a bad block you are stuck.
> > 
> > reiserfs doesn't, but the HD usually has transparently in its firmware.
> > So it hits a bad block; you see an IO error and the next time you hit
> > the block the firmware has mapped in a fresh one from its internal
> > reserves.
> 
> In fact you will typically only see an I/O error if the drive _can't_
> remap the sector anymore, because it has run out. No point in reporting
> a condition that was recovered.
> 
> I'd still say, that if you get bad block errors reported from your disk
> it's long overdue for replacement.
> 
> -- 
> Jens Axboe

Well, I have been fighting this for a while now, its just that today it
finally hit /home in a big way :( basically its giving a DoS trying 
to compile stuff (which needs to write 25Mb+ library files)

The drive gives the patented IBM "replace me" audio and the kernel graces
me with these little chums:

May 24 14:50:22 kloof kernel: hda: dma_intr: status=0x51 { DriveReady SeekComplete Error }
May 24 14:50:22 kloof kernel: hda: dma_intr: error=0x40 { UncorrectableError }, LBAsect=78294495, sector=957496
May 24 14:50:22 kloof kernel: end_request: I/O error, dev 03:08 (hda), sector 957496
May 24 14:50:22 kloof kernel: hda: dma_intr: status=0x51 { DriveReady SeekComplete Error }
May 24 14:50:23 kloof kernel: hda: dma_intr: error=0x40 { UncorrectableError }, LBAsect=78294495, sector=957504
May 24 14:50:23 kloof kernel: end_request: I/O error, dev 03:08 (hda), sector 957504
May 24 14:50:23 kloof kernel: hda: dma_intr: status=0x51 { DriveReady SeekComplete Error }
May 24 14:50:23 kloof kernel: hda: dma_intr: error=0x40 { UncorrectableError }, LBAsect=78294495, sector=957512

I already knew that the drive was rooted by using the IBM DFT tool.
I am backing up as I type. Then, roll the dice with yet another 
IBM drive :-/
 

-- 
---------------------------------------------------
It's the question, http://witme.sourceforge.net
If you think education is expensive, try ignorance.
		-- Derek Bok, president of Harvard


  reply	other threads:[~2001-05-24 12:09 UTC|newest]

Thread overview: 24+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-05-24  3:25 Dying disk and filesystem choice monkeyiq
2001-05-24  6:03 ` Hans Reiser
2001-05-24  6:58 ` Andreas Dilger
2001-05-24  8:31   ` Andi Kleen
2001-05-24 10:19     ` Jens Axboe
2001-05-24 12:08       ` monkeyiq [this message]
2001-05-24 15:46       ` Jonathan Lundell
2001-05-24 15:50     ` Jonathan Lundell
2001-05-24 15:56       ` Andi Kleen
2001-05-24 16:13         ` Jonathan Lundell
2001-05-24 16:53     ` Hans Reiser
2001-05-24 17:16       ` David Rees
2001-05-24 19:03       ` J Sloan
2001-05-24 20:54         ` Hans Reiser
2001-05-24 19:46       ` Erik Mouw
2001-05-24 21:24         ` Hans Reiser
2001-05-24 22:16         ` Alan Cox
2001-05-25 13:21           ` Chris Mason
2001-05-25 16:21             ` Hans Reiser
2001-05-25 16:58               ` Chris Mason
2001-05-25 17:42                 ` Hans Reiser
2001-05-25 11:29         ` Juan Quintela
2001-05-24 21:35       ` monkeyiq
  -- strict thread matches above, loose matches on Subject: below --
2001-05-24 17:30 Cress, Andrew R

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=m3eltfymo1.fsf@kloof.cr.au \
    --to=monkeyiq@users.sourceforge.net \
    --cc=adilger@turbolinux.com \
    --cc=ak@suse.de \
    --cc=axboe@suse.de \
    --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