June 30, 20206 yr Recently, every time I run mover I get thousands of entries like this: Specified filename /mnt/disk2/appdata/PlexMediaServer/Library/Application Support/Plex Media Se rver/Metadata/Albums/56cf780cd115e404elle.bundle/Contents/_combined/ tracks/ 72e2fe80586257df4gf44g8g2f510da2c387 c693/ lyrics/com.plexapp.agent does not exist. Specified filename /mnt/disk2/appdata/PlexMediaServer/Library/Application Support/Plex Media Server/Metadata/Albums/5/8c5c6aade348b67@[email protected]/Contents/_combined/posters/com.plexapp.agents.lastfm/aed32da8df515e04cc3bd61g27b7c3fd7e6be does not exist. And then in the system log I get thousands of entries saying: shfs: share cache full Minimum free space is 100 GB but I have 428 GB free space available on my cache disk.
June 30, 20206 yr Possibly corrupt filesystem on cache, no way to tell without the diagnostics zip file.
June 30, 20206 yr Author 1 hour ago, jonathanm said: Possibly corrupt filesystem on cache, no way to tell without the diagnostics zip file. Hmmm, but it's talking about files not on the cache. Here's the diagnostics. fs-diagnostics-20200630-1852.zip
June 30, 20206 yr 3 hours ago, cinereus said: shfs: share cache full This refers to the share being written to minimum space setting (i.e. cache has less free space than the share's minimum free space setting), when the cache device/pool itself is full (i.e. hitting the cache floor setting) you get: shfs: cache disk full
June 30, 20206 yr Author 1 hour ago, johnnie.black said: This refers to the share being written to minimum space setting (i.e. cache has less free space than the share's minimum free space setting), when the cache device/pool itself is full (i.e. hitting the cache floor setting) you get: That's what I thought. The minimum free space setting is, as I said, 100 GB and I have 428 GB. So what's going on?
June 30, 20206 yr The more logical explanations are either the error comes from another share or the cache was fuller at some point in time, your syslog is heavily spammed with various errors and there's time missing, you can reboot, run the mover again a post new diags.
June 30, 20206 yr Author Other shares are cache yes not prefer and none have min space more than 100 GB. I have stopped and started the array to try and fix this but can still see the log filling up with entires in real time while mover is throwing errors.
June 30, 20206 yr 1 minute ago, cinereus said: I have stopped and started the array to try and fix this That won't clear the log, please reboot and post new diags after running the mover.
July 1, 20206 yr Author 10 hours ago, johnnie.black said: That won't clear the log, please reboot and post new diags after running the mover. Okay thanks. mover doesn't seem to do anything now. fs-diagnostics-20200701-1038.zip
July 1, 20206 yr Mover logging is disable, enable and run again. Also if possible stop dropbox from spamming the log with errors.
July 1, 20206 yr Author 5 minutes ago, johnnie.black said: Mover logging is disable, enable and run again. Also if possible stop dropbox from spamming the log with errors. My bad. I was trying to disable the mover schedule and accidentally disabled logging instead. This is what I get in the log now: mover: started shell-init: error retrieving current directory: getcwd: cannot access parent directories: No such file or directory shell-init: error retrieving current directory: getcwd: cannot access parent directories: No such file or directory shell-init: error retrieving current directory: getcwd: cannot access parent directories: No such file or directory shell-init: error retrieving current directory: getcwd: cannot access parent directories: No such file or directory shell-init: error retrieving current directory: getcwd: cannot access parent directories: No such file or directory shell-init: error retrieving current directory: getcwd: cannot access parent directories: No such file or directory shell-init: error retrieving current directory: getcwd: cannot access parent directories: No such file or directory shell-init: error retrieving current directory: getcwd: cannot access parent directories: No such file or directory shell-init: error retrieving current directory: getcwd: cannot access parent directories: No such file or directory shell-init: error retrieving current directory: getcwd: cannot access parent directories: No such file or directory shell-init: error retrieving current directory: getcwd: cannot access parent directories: No such file or directory shell-init: error retrieving current directory: getcwd: cannot access parent directories: No such file or directory shell-init: error retrieving current directory: getcwd: cannot access parent directories: No such file or directory shell-init: error retrieving current directory: getcwd: cannot access parent directories: No such file or directory mover: finished I'm working with kenji to try and fix Dropbox.
July 1, 20206 yr 7 minutes ago, cinereus said: shell-init: error retrieving current directory: getcwd: cannot access parent directories: No such file or directory Sorry, no idea what this error means, you can try again after booting in safe mode.
Archived
This topic is now archived and is closed to further replies.