(solved, answered)  If I move files around on the server or transfer files from an attached and mounted drive, which are not part of the array, using the linux move (mv), command, will the parity be updated?  Some small tests seem to indicate to me that parity does not update and after moving files I would need to rebuild parity manually.

I hope I'm wrong and can use the linux commands available on all files and folders, except where unraid may restrict certain syntax or options.

Thanks,

Vic  

If I move files around on the server or transfer files from an attached and mounted drive, which are not part of the array, using the linux move (mv), command, will the parity be updated?  Some small tests seem to indicate to me that parity does not update and after moving files I would need to rebuild parity manually.

I hope I'm wrong and can use the linux commands available on all files and folders, except where unraid may restrict certain syntax or options.

Thanks,

Vic   

Parity is kept up to date real time and the mv command does not change that fact.  You are fine to use the mv command all you like.

If I move files around on the server or transfer files from an attached and mounted drive, which are not part of the array, using the linux move (mv), command, will the parity be updated?  Some small tests seem to indicate to me that parity does not update and after moving files I would need to rebuild parity manually.

I hope I'm wrong and can use the linux commands available on all files and folders, except where unraid may restrict certain syntax or options.

Thanks,

Vic   

If you are not moving files to the protected array, parity is not involved at all.  In other words, you can move files all day long on folders on your attached drive that is not part of the array and parity is unchanged.

 

If however you move a file from your disk that is not part of the array to any that are in the protected array, then parity is kept up to date on the protected disks.

 

protected disks are those accessed under /mnt/user (for the user-shares) or /mnt/disk1, /mnt/disk2, /mnt/disk3, etc. (for the disk shares)

 

Joe L.