/cc linux-raid
---------- Forwarded message ----------
From: Gandalf Corvotempesta <gandalf.corvotempesta@xxxxxxxxx>
Date: 2017-03-19 11:42 GMT+01:00
Subject: Re: component device mismatches found
To: Wols Lists <antlists@xxxxxxxxxxxxxxx>
2017-03-19 11:21 GMT+01:00 Wols Lists <antlists@xxxxxxxxxxxxxxx>:
> mdadm --detail /dev/md/0
# mdadm --detail /dev/md0
/dev/md0:
Version : 1.2
Creation Time : Mon Jul 25 12:55:48 2016
Raid Level : raid1
Array Size : 488382841 (465.76 GiB 500.10 GB)
Used Dev Size : 488382841 (465.76 GiB 500.10 GB)
Raid Devices : 3
Total Devices : 3
Persistence : Superblock is persistent
Update Time : Sun Mar 19 11:38:53 2017
State : clean, recovering
Active Devices : 3
Working Devices : 3
Failed Devices : 0
Spare Devices : 0
Rebuild Status : 83% complete
Name : x:0 (local to host x)
UUID : b2a5ed53:42890b73:dc6de22a:1ac12524
Events : 29170
Number Major Minor RaidDevice State
0 8 1 0 active sync /dev/sda1
1 8 17 1 active sync /dev/sdb1
2 8 33 2 active sync /dev/sdc1
keep in mind that:
1) i've done a check this morning, after seeing the mismatch error in syslog
2) even this check has triggered a rebuild, probably due to the same mismatch.
3) SMART doesn't report any errors,
4) disks are "new", 5600 hours.
5) swap is still unused
--
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
