December 15, 20241 yr I have nextcloud docker installed, it has it's own share Nextcloud that is set to cache -> array File activity plugin is reporting: ** /mnt/user/Nextcloud ** Dec 15 15:20:00 OPEN => /mnt/disk1/Nextcloud/owncloud.db Dec 15 15:20:00 MODIFY => /mnt/disk1/Nextcloud/owncloud.db Dec 15 15:20:00 MODIFY => /mnt/disk1/Nextcloud/owncloud.db Dec 15 15:20:00 MODIFY => /mnt/disk1/Nextcloud/owncloud.db Dec 15 15:20:00 MODIFY => /mnt/disk1/Nextcloud/owncloud.db Dec 15 15:20:00 MODIFY => /mnt/disk1/Nextcloud/owncloud.db Dec 15 15:20:00 MODIFY => /mnt/disk1/Nextcloud/owncloud.db Dec 15 15:20:00 MODIFY => /mnt/disk1/Nextcloud/owncloud.db Dec 15 15:20:00 MODIFY => /mnt/disk1/Nextcloud/owncloud.db Dec 15 15:25:00 OPEN => /mnt/disk1/Nextcloud/owncloud.db Dec 15 15:25:00 MODIFY => /mnt/disk1/Nextcloud/owncloud.db Dec 15 15:25:00 MODIFY => /mnt/disk1/Nextcloud/owncloud.db Dec 15 15:25:00 MODIFY => /mnt/disk1/Nextcloud/owncloud.db Dec 15 15:25:00 MODIFY => /mnt/disk1/Nextcloud/owncloud.db Dec 15 15:25:00 MODIFY => /mnt/disk1/Nextcloud/owncloud.db Dec 15 15:25:00 MODIFY => /mnt/disk1/Nextcloud/owncloud.db Dec 15 15:25:00 MODIFY => /mnt/disk1/Nextcloud/owncloud.db Dec 15 15:25:00 MODIFY => /mnt/disk1/Nextcloud/owncloud.db Mover runs every day and moves from cache to array as expected. Nextcloud seems to modify owncloud.db quite frequently even if not used causing array disk1 and parity to spin up. It seems that any modification to a file already present on the array is done straight to array, I was hoping the modified file would be written to my cache disk (SSD) and not the array but that doesn't seem the case - any way around this please to prevent the spin-ups of disk1 and parity? Edited December 15, 20241 yr by fireplex
December 16, 20241 yr Community Expert If you want to keep disk1 and parity from spinning up because of that file, yes.
December 16, 20241 yr Author OK. Problem is mover will then move it back to array. Would just be good if a modified file on the array is written to cache rather than array but guess it just doesn't work that way,
December 16, 20241 yr Community Expert 1 hour ago, fireplex said: Problem is mover will then move it back to array. You would need to set that share to cache=only.
December 16, 20241 yr Community Expert Solution 3 hours ago, fireplex said: Would just be good if a modified file on the array is written to cache rather than array but guess it just doesn't work that way, Unfortunately not. Existing files are modified in place.
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.