public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: DervishD <lkml@dervishd.net>
To: jerome lacoste <jerome.lacoste@gmail.com>
Cc: lkml <linux-kernel@vger.kernel.org>
Subject: Re: Huge unreliability - does Linux have something to do with it?
Date: Fri, 4 Feb 2005 12:51:54 +0100	[thread overview]
Message-ID: <20050204115154.GB625@DervishD> (raw)
In-Reply-To: <5a2cf1f605020401037aa610b9@mail.gmail.com>

    Hi Jerome :)

 * jerome lacoste <jerome.lacoste@gmail.com> dixit:
> [Sorry for the sensational title]

    It catched my attention ;)))
 
> I halted the machine correctly yesterday night. I never dropped the
> box in 3 years. Am I just being unlucky? Or could the fact that I am
> using Linux on the box affect the reliability in some ways on that
> particular hardware (Dell Inspiron 8100)? I run Linux on 3 other
> computers and never had single problems with them.

    Well, Linux may stress the hardware more than other operating
systems because it tries to optimize usage and performance. But in
this particular case I will think you are very unlucky O:) I've seen
that before, unfortunately.
 
> Could a hardware failure look like bad sectors to fsck?

    Yes, depending on the hardware failure.

> (*) I accept tips on discovering and maybe recovering which files have
> been taken out of my system...

    You should use 'integrit' (http://integrit.sourceforge.net). I
use it to know whether a file whose contents shouldn't change has
changed, but it has more usages. And use memtest86 (there are two
versions out there) to check your RAM, just in case. Bad RAM can
cause 'apparent' hardware failures. A bad RAM chip can cause disk
errors (if you write to disk from *bad* RAM, you'll write *bad* data)
and other failures. Use 'integrit', read the documentation for
details.

    Good luck, you'll need it with that laptop :(

    Raúl Núñez de Arenas Coronado

-- 
Linux Registered User 88736
http://www.dervishd.net & http://www.pleyades.net/
It's my PC and I'll cry if I want to...

  parent reply	other threads:[~2005-02-04 11:55 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-02-04  9:03 Huge unreliability - does Linux have something to do with it? jerome lacoste
2005-02-04  9:20 ` Julien Banchet
2005-02-04 10:31 ` Jim Nelson
2005-02-04 10:45 ` Bernd Eckenfels
2005-02-04 11:28   ` jerome lacoste
2005-02-04 17:13     ` Horst von Brand
2005-02-04 11:27 ` Andre Tomt
2005-02-04 11:51 ` DervishD [this message]
2005-02-04 12:18 ` Wakko Warner
2005-02-04 14:44   ` Dmitry Torokhov
2005-02-06 15:58     ` Dell Inspiron sensors (was: Re: Huge unreliability - does Linux have something to do with it?) Giuseppe Bilotta
2005-02-06 16:58       ` kernel
2005-02-06 21:58         ` Giuseppe Bilotta
2005-02-05 10:38   ` Huge unreliability - does Linux have something to do with it? jerome lacoste
2005-02-05 12:27   ` Willy Tarreau
2005-02-05 15:11     ` Wakko Warner

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=20050204115154.GB625@DervishD \
    --to=lkml@dervishd.net \
    --cc=jerome.lacoste@gmail.com \
    --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