From: Mark Nipper <nipsy@bitgnome.net>
To: "Ing. Gianluca Alberici" <alberici@abinetworks.biz>
Cc: linux-kernel@vger.kernel.org
Subject: Re: Bad disks or bug ?
Date: Tue, 11 Jan 2005 07:00:05 -0600 [thread overview]
Message-ID: <20050111130005.GB87982@king.bitgnome.net> (raw)
In-Reply-To: <41E3C90A.2010703@abinetworks.biz>
On 11 Jan 2005, Ing. Gianluca Alberici wrote:
> How do you explain that ? Overload on hdb due to mirroring and surface
> degradation ?
> OR a kind of vodoo on my hdbs ?
Is it possible that hdb is closer to a high heat source
or is not being cooled as hda if all these machines are the same
case design?
--
Mark Nipper e-contacts:
4475 Carter Creek Parkway nipsy@bitgnome.net
Apartment 724 http://nipsy.bitgnome.net/
Bryan, Texas, 77802-4481 AIM/Yahoo: texasnipsy ICQ: 66971617
(979)575-3193 MSN: nipsy@tamu.edu
-----BEGIN GEEK CODE BLOCK-----
Version: 3.1
GG/IT d- s++:+ a- C++$ UBL++++$ P--->+++ L+++$ !E---
W++(--) N+ o K++ w(---) O++ M V(--) PS+++(+) PE(--)
Y+ PGP t+ 5 X R tv b+++@ DI+(++) D+ G e h r++ y+(**)
------END GEEK CODE BLOCK------
---begin random quote of the moment---
"That we are not much sicker and much madder than we are is
due exclusively to that most blessed and blessing of all
natural graces, sleep."
-- Aldous Huxley
----end random quote of the moment----
next prev parent reply other threads:[~2005-01-11 13:00 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-01-11 12:39 Bad disks or bug ? Ing. Gianluca Alberici
2005-01-11 13:00 ` Mark Nipper [this message]
2005-01-11 13:02 ` Ing. Gianluca Alberici
[not found] ` <41E3D2A7.3000002@sgi.com>
2005-01-11 13:24 ` Ing. Gianluca Alberici
2005-01-11 14:23 ` Bill Davidsen
[not found] <Pine.LNX.4.61.0501111452500.23213@alexandria.physik.uni-oldenburg.de>
2005-01-11 15:07 ` Ing. Gianluca Alberici
-- strict thread matches above, loose matches on Subject: below --
2005-01-11 12:18 Ing. Gianluca Alberici
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=20050111130005.GB87982@king.bitgnome.net \
--to=nipsy@bitgnome.net \
--cc=alberici@abinetworks.biz \
--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;
as well as URLs for NNTP newsgroup(s).