From: Roman Mamedov <rm@romanrm.ru>
To: Steven Haigh <netwiz@crc.id.au>
Cc: linux-raid@vger.kernel.org
Subject: Re: SMART, RAID and real world experience of failures.
Date: Fri, 6 Jan 2012 06:42:22 +0600 [thread overview]
Message-ID: <20120106064222.38c0f1b5@natsu> (raw)
In-Reply-To: <4F063808.6040000@crc.id.au>
[-- Attachment #1: Type: text/plain, Size: 1275 bytes --]
On Fri, 06 Jan 2012 10:53:44 +1100
Steven Haigh <netwiz@crc.id.au> wrote:
> So, in the spirit of experimentation, I did the following:
> # mdadm /dev/md2 --manage --fail /dev/sdd
> # mdadm /dev/md2 --manage --remove /dev/sdd
> # dd if=/dev/zero of=/dev/sdd bs=10M
> # mdadm /dev/md2 --manage --add /dev/sdd
Congratulations on doing absolutely the right thing, IMO :)
> Has the sector with the read failure been remapped and hidden from view?
More likely the drive decided the sector wasn't bad, after all. E.g. by overwriting the sector and thus allowing the drive to throw away old user data from it, you have also let the drive to rewrite the ECC or system area of that sector, or whatever they have today in hard drives on the low level.
If it was indeed remapped, then the logic would also require an increase in Reallocated_Sector_Ct; but SMART attribute readings do have a lot of peculiarities, many of which are also vendor-specific.
> Is it still (more?) likely to fail in the near future?
In my experience not at all, unless you start getting stuff like this every week.
--
With respect,
Roman
~~~~~~~~~~~~~~~~~~~~~~~~~~~
"Stallman had a printer,
with code he could not see.
So he began to tinker,
and set the software free."
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 198 bytes --]
next prev parent reply other threads:[~2012-01-06 0:42 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-01-05 23:53 SMART, RAID and real world experience of failures Steven Haigh
2012-01-06 0:42 ` Roman Mamedov [this message]
2012-01-06 11:22 ` Peter Grandi
2012-01-06 11:40 ` Steven Haigh
2012-01-06 13:38 ` Phil Turmel
2012-01-09 14:50 ` Peter Grandi
2012-01-09 16:37 ` Phil Turmel
2012-01-09 20:23 ` Peter Grandi
2012-01-09 13:59 ` Peter Grandi
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=20120106064222.38c0f1b5@natsu \
--to=rm@romanrm.ru \
--cc=linux-raid@vger.kernel.org \
--cc=netwiz@crc.id.au \
/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).