On 08/02/15 10:04, Roman Mamedov wrote:
On Sun, 08 Feb 2015 09:39:47 +1100
Eyal Lebedinsky <eyal@xxxxxxxxxxxxxx> wrote:
The error did not show up during normal operation (or during scrub), only during the smartctl long test.
What triggered the error for you?
Just appeared during boot-up after a reboot (after 50 days uptime) which was
performed for some hardware upgrades (RAM, SATA controller). The error doesn't
go away after swapping the SATA controller for different one.
I looked up the size of the different parts of the RAID to arrive at that conclusion. Dumping the sectors
around the bad area also showed it to be all zeroes.
I wouldn't expect mdadm to have any headers or unused areas as far as 133 MB
into a RAID member.
You can also read the earlier discussion starting 26/Feb/14:
Subject: how to handle bad sectors in md control areas?
cheers
--
Eyal Lebedinsky (eyal@xxxxxxxxxxxxxx)
--
To unsubscribe from this list: send the line "unsubscribe linux-raid" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html