From: "Ing. Gianluca Alberici" <alberici@abinetworks.biz>
To: stamer@physnet.physik.uni-oldenburg.de, linux-kernel@vger.kernel.org
Subject: Re: Bad disks or bug ?
Date: Tue, 11 Jan 2005 16:07:33 +0100 [thread overview]
Message-ID: <41E3EBB5.5030305@abinetworks.biz> (raw)
In-Reply-To: <Pine.LNX.4.61.0501111452500.23213@alexandria.physik.uni-oldenburg.de>
Heinrich,
Your analysis shows you know well what we're talking about and i think
finally
you gave the optimal explanation...
I know very well the problems of the IBM DTLA series (i have a dozen of
zombies here...)
and was mainly concerned about Maxtor disks.
Finally i agree it must be something that has to do with the use of
hardware and/or firmware...
I will of course substitute my backup drive immediately !
Regards and thanks,
Gianluca
Heinrich Stamerjohanns wrote:
>Der Gianluca,
>
>I guess you have an IBM Deskstar (or now Hitachi), possibly a DTLA-307045?
>
>We have the same setup: main disk is /dev/hda, backup disk (every night)
>is /dev/hdb.
>
>One just crashed yesterday, it is the fifth IBM (out of five) that
>crashed (this is already a replacement disk...).
>Don't worry your IBM /dev/hda will crash sooner or later as well ;)
>
>But when I investigated after the first crash, I read something like
>that these disk especially do not cope with the situation that they are
>only infrequently used, but then heavily (no use at all, then continous
>backup..). The firmware has supposedly changed since then, but it
>has not helped the replacment drive.
>So I guess your problem with /dev/hdb is rather a hardware than
>a software problem.
>
>To be sure you could make /dev/hdb your main disk and backup to /dev/hda.
>I am quite sure that /dev/hda will give up first then. (But it happened to
>us that the main drive died two days later, without a replaced backup
>drive...)
>
>Greetings, Heinrich
>
>
>--
> Dr. Heinrich Stamerjohanns Tel. +49-441-798-4276
> Institute for Science Networking stamer@uni-oldenburg.de
> University of Oldenburg http://isn.uni-oldenburg.de/~stamer
>
>
>
next parent reply other threads:[~2005-01-11 15:12 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <Pine.LNX.4.61.0501111452500.23213@alexandria.physik.uni-oldenburg.de>
2005-01-11 15:07 ` Ing. Gianluca Alberici [this message]
2005-01-11 12:39 Bad disks or bug ? Ing. Gianluca Alberici
2005-01-11 13:00 ` Mark Nipper
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
-- 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=41E3EBB5.5030305@abinetworks.biz \
--to=alberici@abinetworks.biz \
--cc=linux-kernel@vger.kernel.org \
--cc=stamer@physnet.physik.uni-oldenburg.de \
/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).