Kit,

With the growing size of disk drives, and a more sectors allocated to
reserve sectors, the number of defects alone is not a big concern,
expecially if they are PRIMARY defects (found at manufacture-time).
What would be of concern, is an increase in the number of GROWN defects
over a short period of time.  Unfortunately, it is quite common for one
defect to cause a disk to be replaced, when it could be remapped without
the expense and trouble of a field replacement.

The automatic remapping of grown defects is a feature of SCSI disks, but
may not be configured in the disk's mode pages.  The mode pages can be
changed without affecting the content of the disk (with the exception of
size & sector mapping parameters).  There are several Linux tools to
read/set mode pages, among which is 'sgmode' from
http://scsirastools.sf.net.

As a guess, it appears that you had a grown defect occur on one of your
disks, but the remapping was not set to occur automatically on that
disk, so a write never finished.

Andy


-----Original Message-----
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of Kit Gerrits
Sent: Monday, January 31, 2005 9:28 AM
To: linux-scsi@vger.kernel.org
Subject: Disk errors


Exactly how many errors is a SCSI disk allowed to have?

I have a PE2400 with a PERC2/Si with 4x9GB

My disks show:
AFA0> disk show defects 0
Executing: disk show defects (ID=0)
Number of PRIMARY defects on drive: 1912
Number of GROWN defects on drive: 0

AFA0> disk show defects 1
Executing: disk show defects (ID=1)
Number of PRIMARY defects on drive: 952
Number of GROWN defects on drive: 1

AFA0> disk show defects 2
Executing: disk show defects (ID=2)
Number of PRIMARY defects on drive: 2457
Number of GROWN defects on drive: 0

AFA0> disk show defects 3
Executing: disk show defects (ID=3)
Number of PRIMARY defects on drive: 2794
Number of GROWN defects on drive: 0

The reason I ask is tha tmy O/S (RedHat Enterprise Linux 3.0) has
recently
hung with the error:

I/O Error Dev 08:05 Sector 529712

I would assume that this error is generated by the harddrive, but
shouldn't
the controller catch SCSI errors (and relocate sectors automagically)?

Thanks in advance,

Kit Gerrits

[EMAIL PROTECTED]

-
To unsubscribe from this list: send the line "unsubscribe linux-scsi" in
the body of a message to [EMAIL PROTECTED]
More majordomo info at  http://vger.kernel.org/majordomo-info.html
-
To unsubscribe from this list: send the line "unsubscribe linux-scsi" in
the body of a message to [EMAIL PROTECTED]
More majordomo info at  http://vger.kernel.org/majordomo-info.html

Reply via email to