From: jerome lacoste <jerome.lacoste@gmail.com>
To: Bernd Eckenfels <ecki-news2005-01@lina.inka.de>
Cc: linux-kernel@vger.kernel.org
Subject: Re: Huge unreliability - does Linux have something to do with it?
Date: Fri, 4 Feb 2005 12:28:07 +0100 [thread overview]
Message-ID: <5a2cf1f60502040328aaf6c9f@mail.gmail.com> (raw)
In-Reply-To: <E1Cx0xm-0000GD-00@calista.eckenfels.6bone.ka-ip.net>
>> Could a hardware failure look like bad sectors to fsck?
>
> A failure of the bus or a former sporadic error can cause defective fs, but
> normally you have a read error in fsck no structure error.
>
> Are you using hdparm? is the system perhaps overheating or overclocked?
no overclock
hdparm is used but I cannot tell you exactly what the config is (now
machine has been running memtest for 1.5 hour). I don't think I use
special option: probably the defaults in my config file (mult_sect 16,
dma on, write_cache off).
overheating: perhaps. The machine is hot and running many hours per
day (usually 12-16). It s running the fans very often, but it's always
been like that. I've tried to control the fan, but then the
temperature goes high very quickly. So I let the fans run.
next prev parent reply other threads:[~2005-02-04 11:28 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-02-04 9:03 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 [this message]
2005-02-04 17:13 ` Horst von Brand
2005-02-04 11:27 ` Andre Tomt
2005-02-04 11:51 ` DervishD
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=5a2cf1f60502040328aaf6c9f@mail.gmail.com \
--to=jerome.lacoste@gmail.com \
--cc=ecki-news2005-01@lina.inka.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
Powered by JetHome