From: Rogier Wolff <R.E.Wolff@BitWizard.nl>
To: Xavier Bestel <xavier.bestel@free.fr>
Cc: venom@sns.it, louie miranda <louie@chikka.com>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: Hi is this critical??
Date: Tue, 17 Sep 2002 10:40:10 +0200 [thread overview]
Message-ID: <20020917104010.A6175@bitwizard.nl> (raw)
In-Reply-To: <1032184041.7199.14.camel@bip>
On Mon, Sep 16, 2002 at 03:47:20PM +0200, Xavier Bestel wrote:
> Le lun 16/09/2002 à 15:37, venom@sns.it a écrit :
> >
> > yes, this is critical.
> > It means that your HD is going to break soon.
> >
>
> Maybe these error messages should be a bit less cryptic for the
> uninitiated. Or is there a userspace utility to convert theses to
> luser-understandable messages ?
The problem is that you're going to leave out details to do this.
This means that even the experts don't know what happened.
>From the reported message I was able to pinpoint the exact spot on
his hdb2 partition where his drive has a bad spot, and I can calculate
the size of his hdb1 partition (In this case probably unneccesary
information, but still...).
If the error message says something like:
"your harddrive hdb seems to be failing. Replace it NOW!"
then I can't make a valid decision about this. I have had a WD 31600
drive which had the trouble that the last 400M would go "bad": Lots of
bad blocks. In that situation I had to monitor the drive to just have
bad blocks in the last 400M or so, while I used only the first 1000M.
(Yes, only for "tmp" stuff.)
I also have a drive that has exactly ONE bad block. Run it through
"badblocks", and you can use the disk just fine. A read-ahead
might hit on the bad block, leading to funny error messages. However
I DO need to know which block.
MAC and Windows both try to give "simple" error messages. As a
knowledgeable person I then am confronted with:
"Something went wrong. Contact your sysadmin if you can't
fix it yourself".
Well, I -=AM=- the sysadmin, and would like to know what went wrong.
Otherwise I can't fix it. This is NOT the way to go.
Roger.
--
** R.E.Wolff@BitWizard.nl ** http://www.BitWizard.nl/ ** +31-15-2137555 **
*-- BitWizard writes Linux device drivers for any device you may have! --*
* The Worlds Ecosystem is a stable system. Stable systems may experience *
* excursions from the stable situation. We are currenly in such an *
* excursion: The stable situation does not include humans. ***************
next prev parent reply other threads:[~2002-09-17 8:35 UTC|newest]
Thread overview: 33+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-09-16 20:05 2.4.19 - not a real problem raptor
2002-09-16 13:31 ` Hi is this critical?? louie miranda
2002-09-16 13:34 ` DevilKin
2002-09-16 13:37 ` venom
2002-09-16 13:47 ` Xavier Bestel
2002-09-16 14:16 ` Mark Veltzer
2002-09-16 14:14 ` Xavier Bestel
2002-09-16 15:57 ` venom
2002-09-16 23:23 ` Nuitari
2002-09-16 18:27 ` jbradford
2002-09-16 22:46 ` venom
2002-09-17 5:18 ` Nuitari
2002-09-17 8:02 ` jbradford
2002-09-17 8:20 ` Andre Hedrick
2002-09-17 10:41 ` Alan Cox
2002-09-17 11:09 ` Russell King
2002-09-17 11:17 ` Alan Cox
2002-09-17 12:02 ` Russell King
2002-09-17 12:17 ` jbradford
2002-09-17 12:02 ` jbradford
2002-09-17 18:39 ` Bill Davidsen
2002-09-18 6:00 ` Daniel Berlin
2002-09-17 17:34 ` Andre Hedrick
2002-09-17 17:54 ` Russell King
2002-09-17 19:30 ` jbradford
2002-09-17 18:34 ` Bill Davidsen
2002-09-18 5:56 ` Daniel Berlin
2002-09-17 18:23 ` Bill Davidsen
2002-09-16 14:43 ` Russell King
2002-09-17 8:40 ` Rogier Wolff [this message]
2002-09-17 9:03 ` jbradford
2002-09-16 14:53 ` Alan Cox
2002-10-05 12:58 ` 2.4.19 - not a real problem Adrian Bunk
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=20020917104010.A6175@bitwizard.nl \
--to=r.e.wolff@bitwizard.nl \
--cc=linux-kernel@vger.kernel.org \
--cc=louie@chikka.com \
--cc=venom@sns.it \
--cc=xavier.bestel@free.fr \
/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