June 2, 201214 yr I just replaced a 1 TB drive with a 3 TB one. Currently it is rebuilding data. This might take some thime. Will the mover script be put on hold during this time automatically or should I manually disable it for this share? What is the best way to do it?
June 2, 201214 yr I just replaced a 1 TB drive with a 3 TB one. Currently it is rebuilding data. This might take some thime. Will the mover script be put on hold during this time automatically or should I manually disable it for this share? What is the best way to do it? I would disable it. Easiest way is to do the following... It will then be disabled until you reboot. type: echo "exit" >/usr/local/sbin/mover
June 2, 201214 yr Author I just replaced a 1 TB drive with a 3 TB one. Currently it is rebuilding data. This might take some thime. Will the mover script be put on hold during this time automatically or should I manually disable it for this share? What is the best way to do it? I would disable it. Easiest way is to do the following... It will then be disabled until you reboot. type: echo "exit" >/usr/local/sbin/mover Thanks Joe. Will it have any consequence for data that is on the cache drive and is ready to be moved next night. Will this data be moved after rebooting?
June 2, 201214 yr I just replaced a 1 TB drive with a 3 TB one. Currently it is rebuilding data. This might take some thime. Will the mover script be put on hold during this time automatically or should I manually disable it for this share? What is the best way to do it? I would disable it. Easiest way is to do the following... It will then be disabled until you reboot. type: echo "exit" >/usr/local/sbin/mover Thanks Joe. Will it have any consequence for data that is on the cache drive and is ready to be moved next night. Will this data be moved after rebooting? It just replaces the mover script with one that does nothing. It has no affect on anything in the cache. What is there will be moved AFTER you reboot to put back the original mover script. (you'll need to reboot to get the mover working once more) You'll not have to worry about the mover until YOU decide you want it back again. If you do not want to reboot, as an alternative, you can rename the mover script rather than replacing it with a script that just exits, Type (instead of the command above) mv /usr/local/sbin/mover /usr/local/sbin/orig_mover Then, when yu want to restore it, type: mv /usr/local/sbin/orig_mover /usr/local/sbin/mover Joe L. Joe L.
June 3, 201214 yr Just to add another option. You could go to the user share page and modify the schedule. The last * means move every day. You can change it to a number 0 to 6 corresponding to days of the week starting with Sunday. So, since it's Saturday you could use 5 meaning it will only run on Fridays. Put it back to a * to get it to run every day again. No reboot required. http://en.wikipedia.org/wiki/Cron#Predefined_scheduling_definitions
June 3, 201214 yr Author Thanks Lionel I will keep that in mind next time. The rebuild has finished. One final question: I should now run a parity-check. Should it be corrective or not? When to use either option?
June 3, 201214 yr Thanks Lionel I will keep that in mind next time. The rebuild has finished. One final question: I should now run a parity-check. Should it be corrective or not? When to use either option? My advice, never use the corrective version first. If multiple non-correcting checks result in the exact same parity failures, and you are sure no disks have had recent failing (un-readable) sectors, then you can perform the correcting check to get it back in sync. Joe L.
June 3, 201214 yr Author Maybe that checkbox should be unchecked by default then? Every time I enter the server's webpage it's checked.
June 3, 201214 yr Maybe that checkbox should be unchecked by default then? Every time I enter the server's webpage it's checked. This is a whole other argument It has been discussed many times on this forum and there are plenty of users who feel the default option should be unticked, however at this stage Tom from limetech has made the executive decision that it will remain ticked by default.
Archived
This topic is now archived and is closed to further replies.