From: "vincent" <hanguozhong@meganovo.com>
To: linux-raid@vger.kernel.org
Subject: raid5:bad sectors after lost power
Date: Thu, 13 Sep 2012 16:43:27 +0800 [thread overview]
Message-ID: <50519cb3.21bf440a.60ca.ffffa83b@mx.google.com> (raw)
[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #1: Type: text/plain; charset=gb2312, Size: 1280 bytes --]
Hi everyone:
I have a problem about raid5.
I created a raid5 with the command ¡°mdadm ¨CCv --chuck=128 /dev/md0 ¨C
l5 ¨Cn4 sd[abcd]¡± for write performance test, the capacity of each disk is
2TB. After the array was created, I modified the strip_catch_size of it to
2048.
Then I used a program to parallel write 150 files to the array, the
speed of each is 1MB/s. Unfortunately, the electricity went off suddenly at
the time. when I turn on the device again, I found the raid5 is in recovery.
When the progress of the recovery went up to 98%, there was a write
error occurred. I used ¡°smartctl ¨CA /dev/sd*¡± to check the heath status
of these disks. I found the ¡°RAW_VALUE¡± of the attribute whose name was
¡°Current_Pending_Sector¡± of sda and sdb were 1.
¡¡¡¡Then I used ¡°HDD_Regenerator¡± to check if there were bad blocks in the
disks. The result of the output indicated that sda and sdb did have a bad
sector.
These disks were used for the first time after purchased. Is it normal
to have bad sectors? Could you please help me?
--
To unsubscribe from this list: send the line "unsubscribe linux-raid" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
next reply other threads:[~2012-09-13 8:43 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-09-13 8:43 vincent [this message]
2012-09-13 8:57 ` raid5:bad sectors after lost power Mathias Buren
2012-09-13 10:48 ` Mikael Abrahamsson
2012-09-13 20:00 ` 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=50519cb3.21bf440a.60ca.ffffa83b@mx.google.com \
--to=hanguozhong@meganovo.com \
--cc=linux-raid@vger.kernel.org \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.