November 11, 20241 yr Hi, I have a file on disk 1: but when reading it (VLC) the disk 1 is not spin up, but the file is somehow reading from cache drive How is this even possible? When browsing cache drive can't find this file Edited November 11, 20241 yr by Vitek
November 11, 20241 yr Community Expert check you shares tab and make sure it set coretly to where you want the file to be at.. you may have a 2nd disk set to be on cache:
November 11, 20241 yr Author 4 minutes ago, bmartino1 said: check you shares tab and make sure it set coretly to where you want the file to be at.. you may have a 2nd disk set to be on cache: Everything looks fine in the media folder settings: also, file browser shows this file is on disk 1 only:
November 11, 20241 yr Community Expert weird... ok, since this is medai... is a docker set to use cache over the array? /mnt/cahce instead of /mnt/user ? double check you docker setting for default apppdata path.
November 11, 20241 yr Author Just now, bmartino1 said: weird... ok, since this is medai... is a docker set to use cache over the array? /mnt/cahce instead of /mnt/user ? double check you docker setting for default apppdata path. My docker settings are correct: This is really weird because everything works as expected for other files, for example, when I open a file that is on disk 2, disk 2 spins up. This weird situation is only for this file.
November 11, 20241 yr Community Expert Go to the Shares page and click on "compute" for appdata, see where the share exists.
November 11, 20241 yr Author 1 minute ago, JorgeB said: Go to the Shares page and click on "compute" for appdata, see where the share exists. The Appdata is on Cache as expected The Media folder is on Array (file is on disk 1) as expected:
November 11, 20241 yr Community Expert Sorry I meant media, if that share only exists on the array, it must be read from the array, unless you have a container/plugin/script caching it.
November 11, 20241 yr Author 20 minutes ago, JorgeB said: Sorry I meant media, if that share only exists on the array, it must be read from the array, unless you have a container/plugin/script caching it. I don't have any caching script/plugin and still, the file is reading from the cache (at least the dashboard is showing reading/writing on cache drive when accessing this file) meanwhile disk 1 where the file is placing is sleeping. That is really weird because when I open other files, data disk is spins up correctly. File activity plugin shows correct disk: But the disk 1 is spin down And the Main tab is showing activity on the Cache drive when accessing this file. My God... Edited November 11, 20241 yr by Vitek
November 11, 20241 yr Community Expert Re-start the array, to clear RAM cache, then type: pv /path/to/that/file > /dev/null And check the GUI activity
November 11, 20241 yr Author 1 hour ago, JorgeB said: Re-start the array, to clear RAM cache, then type: pv /path/to/that/file > /dev/null And check the GUI activity Will check that tomorrow @JorgeB 1. Array restarted, run pv command, first run, disk 1 spin up and the file is accessed from disk 1: 2. second run reading from the cache drive You can see the difference in speed when running command pv for the second time because the cache drive is reading. From now every time I access the file it is accessible from the cache drive, WTF... It seems somehow the file is caching in the cache drive, but again, I don't use any plugin/script for caching... Edited November 11, 20241 yr by Vitek
November 12, 20241 yr Community Expert my only theory is the array is using the cache disk by default. This may be due to docker setting using default path /mnt/cache instead of the fuse symbolic system of /mnt/user... the last thing outside of editing the docker setting is a unraid reboot. Something may be chaced in ram/config like [parity/mover] tuner plugins may be doing something...
November 12, 20241 yr Author 4 hours ago, bmartino1 said: my only theory is the array is using the cache disk by default. This may be due to docker setting using default path /mnt/cache instead of the fuse symbolic system of /mnt/user... the last thing outside of editing the docker setting is a unraid reboot. Something may be chaced in ram/config like [parity/mover] tuner plugins may be doing something... I don't think it is a docker related issue. When I run the file through samba share in VLC, the result is the same. Reboot does not help.
November 12, 20241 yr Community Expert 15 hours ago, Vitek said: You can see the difference in speed when running command pv for the second time because the cache drive is reading. More likely it's getting it from RAM cache, do you see cache read on the GUI stats?
November 12, 20241 yr Author 5 minutes ago, JorgeB said: More likely it's getting it from RAM cache, do you see cache read on the GUI stats? I see cache drive reading on Main tab (the file is on Disk 1)
November 12, 20241 yr Author 1 minute ago, JorgeB said: I'm sorry, no idea what's going on there. Sure, maybe after I update to unraid v7 things will work ok
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.