On Thu, 30 May 2013 14:29:17 +0100 Mark Rogers mark@quarella.co.uk allegedly wrote:
As I understand it, and based on https://raid.wiki.kernel.org/index.php/RAID_Recovery, events is a record of writes to the disks.
If I look at: mdadm --examine /dev/sd[a-z]1 | egrep 'Event|/dev/sd' on one of my machines, I see each of my 4 disks has an event count of 9760, which is good as it means all four disks are "in sync"; if one of them was lower than this it would have missed something. This is what mdadm uses to determine whether to automatically assemble an array.
If I look at: mdadm --query --detail /dev/md0 the value I see for Events is 0.9760, ie the same value (with the 0. suffix). So why the 0. suffix I have no idea but the events value should be non-zero and ever increasing, by the look of things.
Mark
Many thanks for the continued replies. I'm learning. My results are different though. The number of "events" given for each disk seems ok (at 31 for each). I assume the very low number is simply a symptom of the short run time compared to yours. But the results I get for "mdadm --query --detail /dev/mdX" gives three different answers. md0 is 31, md1 is 19 and md2 is 38 (I have three partitions, /boot, swap and /) and, as you can see, no decimals.
I'll keep reading the manual.
Cheers
Mick
---------------------------------------------------------------------
blog: baldric.net gpg fingerprint: FC23 3338 F664 5E66 876B 72C0 0A1F E60B 5BAD D312
---------------------------------------------------------------------