Skip site navigation (1)Skip section navigation (2)
Date:      Sun, 21 Aug 2011 11:48:32 +0200
From:      Matthias Andree <ma@dt.e-technik.uni-dortmund.de>
To:        freebsd-stable@freebsd.org
Subject:   Re: bad sector in gmirror HDD
Message-ID:  <4E50D470.4090800@dt.e-technik.uni-dortmund.de>
In-Reply-To: <4774BC00-F32B-4BF4-A955-3728F885CAA1@langille.org>
References:  <1B4FC0D8-60E6-49DA-BC52-688052C4DA51@langille.org>	<20110819232125.GA4965@icarus.home.lan>	<B6B0AD0F-A74C-4F2C-88B0-101443D7831A@langille.org>	<20110820032438.GA21925@icarus.home.lan> <4774BC00-F32B-4BF4-A955-3728F885CAA1@langille.org>

next in thread | previous in thread | raw e-mail | index | archive | help
Am 20.08.2011 19:34, schrieb Dan Langille:
> This is an older system.  I suspect insufficient ventilation.  I'll look at getting
> a new case fan, if not some HDD fans.

The answer is quite simple, get new drives.

They have gone for some 24000 hours, IOW, at least 3 years (assuming
24x7), and at around 50 °C, they're worn.  After three years, at the
slightest hitch, replace drives, before Something Bad[tm] happens.
You'll get faster replacements anyhow :)


On a related note, since this is about gmirror:

Linux has a similar subsystem in place called the drive mapper (dm),
with user-space tools mdadm.  The whole rig (kernel + user space)
supports various RAID levels through modules, the gmirror equivalent
being raid1 -- and that module somewhat recently acquired an interesting
*feature:* it can automatically rewrite broken sectors.  Meaning that
when it sees a read error on one drive, it will read the block from the
intact other drive and re-write it on the faulty drive so that it gets
reallocated (assuming nobody turned the drive's ARWE feature off).
Perhaps that's a useful feature for gmirror, too.

> 2848980992 bytes transferred in 127.128503 secs (22410246 bytes/sec)

Eek, someone should fix dd to use proper units and not confuse seconds
(s) with the secans function (sec).

Anyways, that's pretty low by today's standards.  My I/O speeds even on
lowly Samsung 5400/min drives are in excess of 100 MBytes/s, and that's
talking about drives made in 2009.



Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?4E50D470.4090800>