Re: checking md device parity (forced resync) - is it necessary?

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



Mario 'BitKoenig' Holbe wrote:
Tomasz Chmielewski <mangoo@xxxxxxxx> wrote:
# by default, run at 01:06 on the first Sunday of each month.
6 1 1-7 * 7 root [ -x /usr/share/mdadm/checkarray ] &&

You have a quite old version of mdadm. This issue has been fixed in
mdadm (2.5.2-8) unstable from 27 Jul 2006. Current version is mdadm
(2.5.3.git200608202239-2) unstable from 23 Aug 2006.

Since the feature did just appear in mdadm (2.5.2-3) UNRELEASED from
7 Jul 2006 (and even just went to unstable with mdadm (2.5.2-7) unstable
from 20 Jul 2006), it seems you were simply in quite bad luck :)

Yes, I saw somewhere in the changelogs that the issue is fixed.

Still, I can't find 2.5.2-8 anywhere on the mirrors, perhaps it's just a matter of time...


--
Tomasz Chmielewski
http://wpkg.org


-
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

[Index of Archives]     [Linux RAID Wiki]     [ATA RAID]     [Linux SCSI Target Infrastructure]     [Linux Block]     [Linux IDE]     [Linux SCSI]     [Linux Hams]     [Device Mapper]     [Device Mapper Cryptographics]     [Kernel]     [Linux Admin]     [Linux Net]     [GFS]     [RPM]     [git]     [Yosemite Forum]


  Powered by Linux