March 30, 20179 yr I've just copied a file to my SSD cache, and can see the parity reads and writes are increasing on the parity drives, when my understanding was the parity would only be created once the files are moved to the array Is this expected behaviour? My appdata folder lies on my cache drive too, so i don't think it's the dockers causing it
March 30, 20179 yr 3 hours ago, sdamaged said: I've just copied a file to my SSD cache, and can see the parity reads and writes are increasing on the parity drives, when my understanding was the parity would only be created once the files are moved to the array Is this expected behaviour? My appdata folder lies on my cache drive too, so i don't think it's the dockers causing it Not its not expected... How do you know the file wound up on the cache drive?
March 30, 20179 yr Author OK i checked, and it copied it to the array, despite that share being told to use the cache drive. I just checked the cache drive and there isn't much on it, yet every single share is set to use the cache drive
March 30, 20179 yr 3 minutes ago, sdamaged said: OK i checked, and it copied it to the array, despite that share being told to use the cache drive. I just checked the cache drive and there isn't much on it, yet every single share is set to use the cache drive Post your diagnostics. There are also situations where files will automatically go to the array if the file already exists on the array (ie: modifying an existing file on the array)
March 30, 20179 yr Author Thanks Squid I did overwrite some existing files so this explains it for them, but i just did another test with a new file, and it went straight to the array again ba-unraid-diagnostics-20170330-2238.zip
Archived
This topic is now archived and is closed to further replies.