Nicolas George (HE12025-10-27): > Unfortunately, this command has the slight drawback of interrupting the > check, and it will re-start at zero.
I need to correct that statement: Changing the LVM RAID resync rate the effect of stopping the *initial* resync of a newly-created volume. But it seems that for later resyncs, --maxrecoveryrate will stop the process but it will continue where it stopped when restarted. I have written a small program to have some convenient progress information, it can be found here: http://nsup.org/phare/gitweb?p=george/lvmraidtool.git http://nsup.org/phare/gitweb?p=george/lvmraidtool.git;a=blob;f=lvmraidtool;h=438739e3d418b51ac9c1ed913ba7f22ec136057d;hb=bdaffbbdcdd08a99368cc48513be504d9c01f93e Regards, -- Nicolas George
