archive mirror
 help / color / mirror / Atom feed
From: "Ing. Gianluca Alberici" <>
Subject: Bad disks or bug ?
Date: Tue, 11 Jan 2005 13:18:21 +0100	[thread overview]
Message-ID: <> (raw)


i have a little doubt on the following....

/> Sep 10 12:50:30 abivrs0 kernel: hdb: dma_intr: status=0x51 { DriveReady /
/> SeekComplete Error } /
/> Sep 10 12:50:30 abivrs0 kernel: hdb: dma_intr: error=0x40 /

...Of course the explanation of such an error is that drive has bad
sectors and i'd better change it BUT:

I have many production servers running 2.4.27, everything seems OK while
they're new.
After about an year of production many of them (5 of them at present)
begin to show the problem BUT:

1) All of them show the problem on hdb (ALL OF THEM)
2) Never had problems on hda on ANY server, disks are the same, same
size, same partitioning
3) Typically hdb is used as a disk mirror
4) Many times a mkfs.ext3 -c -c solves the problem bringing bad sectors
to a new life !

How do you explain that ? Overload on hdb due to mirroring and surface
degradation ?
OR a kind of vodoo on my hdbs ?

NOTE: Over the internet, when i searched for such errors on disks (not
ramdisks or loop devs) i ALWAYS found problems on hdb !!!

Could it be depending on master-slave configuration ? Kernel bug ? Other ?

What do you say ?

thanks for your time,

Gianluca Alberici

             reply	other threads:[~2005-01-11 12:23 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-01-11 12:18 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]     ` <>
2005-01-11 13:24       ` Ing. Gianluca Alberici
2005-01-11 14:23         ` Bill Davidsen
     [not found] <>
2005-01-11 15:07 ` 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:

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \ \ \ \

* 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).