Bug#556610: Please do incremental checks every night instead of a full monthly one

[Sergey B Kirpichev]

> The main issue which all proposed solutions share is when
> there's a large array, say, md0, and a small array, say,
> md1, both shares the same set of underlying disks, so md
> subystem will not check/repair them in parallel.  In this
> situation, we will never check md1 if checking md0 takes
> more time than we allow in a month (28 days).

What do you think about suggested above solution
(set sync_force_parallel to 1 during cronjobs)?  This workaround
is implemented in the updated (attached) patch.

See also: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=556610#74

BTW, how bad is in general to set
sync_force_parallel to 1 per default?  (Cc'd to Neil Brown.)

I think, it would be nice to end (not pause) check if it's reached
sync_max.  Perhaps, there is deep reasons why md's interface
doesn't work in this way.  Neil, could you explan this a bit?

> I'll think about it all more.

Any news?
-------------- next part --------------
A non-text attachment was scrubbed...
Name: 556610.patch
Type: text/x-diff
Size: 5778 bytes
Desc: not available
URL: <http://lists.alioth.debian.org/pipermail/pkg-mdadm-devel/attachments/20131225/67d2b944/attachment.patch>