October 1, 201312 yr My server does a parity check on the 1st of every month. I thought the mover script was setup to not run during that time. Until I woke up this morning to find the check at around 20% doing 2MB/s because mover is running. I've cancelled the check until tomorrow night, after I've manually disabled the mover. Is there any notification on the system, that I can add to some kind of if statement in the mover script so that it never runs during a rebuild or check? Especially during a rebuild.
October 1, 201312 yr A status changes from /proc/mdcmd that could be queried in the mover script. I don't know what it is off the top of my head, but I know there's a status change there.
October 1, 201312 yr Author I'm still waiting on the mover to finish, I'll restart the parity check and see if any lines in that file change.
October 1, 201312 yr Author In case anyone else is curious, I've added the code below to just after the comment header in the mover file. if ! grep -Fxq "mdResync=0" /proc/mdcmd ; then echo mdResync=0 was not found, resync of some type is running. exit 0 fi I've tested it against a regular parity check, I would expect the mdResync get's updated for rebuilds as I didn't notice any flags in there pertaining to "build".
Archived
This topic is now archived and is closed to further replies.