jang430 Posted September 10, 2020 Share Posted September 10, 2020 No file transfer happening. No move operation happening. All docker apps shut down, all VMs shut down. How do I find out? Quote Link to comment
jang430 Posted September 11, 2020 Author Share Posted September 11, 2020 anyone? Quote Link to comment
SeeGee Posted September 11, 2020 Share Posted September 11, 2020 (edited) Try lsof command. # lsof +D /mnt/<diskwithactivity> Might take a few mins to complete, but it'll show you what files are open/being used on that drive Could also use: # lsof /dev/<active drive> Edited September 11, 2020 by SeeGee Added alternate command Quote Link to comment
jang430 Posted September 11, 2020 Author Share Posted September 11, 2020 (edited) what does this mean? root@Tower:~# lsof +D /mnt/cache/ COMMAND PID USER FD TYPE DEVICE SIZE/OFF NODE NAME shfs 7963 root 16w REG 0,38 4899 5119560 /mnt/cache/appdata/bazarr/app/log/bazarr.log shfs 7963 root 102u REG 0,38 2039808 1235079 /mnt/cache/appdata/bazarr/app/db/bazarr.db mono 15880 nobody 7u REG 0,38 7383040 184002 /mnt/cache/appdata/radarr/nzbdrone.db mono 15880 nobody 9u REG 0,38 65536 5121663 /mnt/cache/appdata/radarr/nzbdrone.db-shm mono 15880 nobody 10u REG 0,38 7383040 184002 /mnt/cache/appdata/radarr/nzbdrone.db mono 15880 nobody 11u REG 0,38 7383040 184002 /mnt/cache/appdata/radarr/nzbdrone.db mono 15880 nobody 12u REG 0,38 59695104 184003 /mnt/cache/appdata/radarr/logs.db mono 15880 nobody 13u REG 0,38 7383040 184002 /mnt/cache/appdata/radarr/nzbdrone.db mono 15880 nobody 15u REG 0,38 7383040 184002 /mnt/cache/appdata/radarr/nzbdrone.db mono 15880 nobody 16u REG 0,38 279848 5129825 /mnt/cache/appdata/radarr/logs.db-wal mono 15880 nobody 17u REG 0,38 32768 5129826 /mnt/cache/appdata/radarr/logs.db-shm mono 15880 nobody 18u REG 0,38 8149280 5121662 /mnt/cache/appdata/radarr/nzbdrone.db-wal mono 16461 nobody 4u REG 0,38 3247104 145178 /mnt/cache/appdata/sonarr/logs.db mono 16461 nobody 5u REG 0,38 113882000 145180 /mnt/cache/appdata/sonarr/logs.db-wal mono 16461 nobody 7u REG 0,38 3247104 145178 /mnt/cache/appdata/sonarr/logs.db mono 16461 nobody 9u REG 0,38 32768 145179 /mnt/cache/appdata/sonarr/logs.db-shm mono 16461 nobody 12u REG 0,38 21349376 147078 /mnt/cache/appdata/sonarr/nzbdrone.db mono 16461 nobody 13u REG 0,38 21969256 5124146 /mnt/cache/appdata/sonarr/nzbdrone.db-wal mono 16461 nobody 14u REG 0,38 21349376 147078 /mnt/cache/appdata/sonarr/nzbdrone.db mono 16461 nobody 16u REG 0,38 21969256 5124146 /mnt/cache/appdata/sonarr/nzbdrone.db-wal mono 16461 nobody 17u REG 0,38 196608 5124147 /mnt/cache/appdata/sonarr/nzbdrone.db-shm mono 16461 nobody 18u REG 0,38 21349376 147078 /mnt/cache/appdata/sonarr/nzbdrone.db mono 16461 nobody 19u REG 0,38 21969256 5124146 /mnt/cache/appdata/sonarr/nzbdrone.db-wal mono 16461 nobody 21u REG 0,38 21349376 147078 /mnt/cache/appdata/sonarr/nzbdrone.db mono 16461 nobody 22u REG 0,38 21349376 147078 /mnt/cache/appdata/sonarr/nzbdrone.db root@Tower:~# lsof /dev/nvme0n1p1 COMMAND PID USER FD TYPE DEVICE SIZE/OFF NODE NAME shfs 7963 root 16w REG 0,38 4899 5119560 /mnt/cache/appdata/bazarr/app/log/bazarr.log shfs 7963 root 102u REG 0,38 2039808 1235079 /mnt/cache/appdata/bazarr/app/db/bazarr.db mono 15880 nobody 7u REG 0,38 7383040 184002 /config/nzbdrone.db mono 15880 nobody 9u REG 0,38 65536 5121663 /config/nzbdrone.db-shm mono 15880 nobody 10u REG 0,38 7383040 184002 /config/nzbdrone.db mono 15880 nobody 11u REG 0,38 7383040 184002 /config/nzbdrone.db mono 15880 nobody 12u REG 0,38 59740160 184003 /config/logs.db mono 15880 nobody 13u REG 0,38 7383040 184002 /config/nzbdrone.db mono 15880 nobody 15u REG 0,38 7383040 184002 /config/nzbdrone.db mono 15880 nobody 16u REG 0,38 13656 5129851 /config/logs.db-wal mono 15880 nobody 17u REG 0,38 32768 5129852 /config/logs.db-shm mono 15880 nobody 18u REG 0,38 8149280 5121662 /config/nzbdrone.db-wal mono 16461 nobody 4u REG 0,38 3247104 145178 /config/logs.db mono 16461 nobody 5u REG 0,38 113882000 145180 /config/logs.db-wal mono 16461 nobody 7u REG 0,38 3247104 145178 /config/logs.db mono 16461 nobody 9u REG 0,38 32768 145179 /config/logs.db-shm mono 16461 nobody 12u REG 0,38 21349376 147078 /config/nzbdrone.db mono 16461 nobody 13u REG 0,38 21969256 5124146 /config/nzbdrone.db-wal mono 16461 nobody 14u REG 0,38 21349376 147078 /config/nzbdrone.db mono 16461 nobody 16u REG 0,38 21969256 5124146 /config/nzbdrone.db-wal mono 16461 nobody 17u REG 0,38 196608 5124147 /config/nzbdrone.db-shm mono 16461 nobody 18u REG 0,38 21349376 147078 /config/nzbdrone.db mono 16461 nobody 19u REG 0,38 21969256 5124146 /config/nzbdrone.db-wal mono 16461 nobody 21u REG 0,38 21349376 147078 /config/nzbdrone.db mono 16461 nobody 22u REG 0,38 21349376 147078 /config/nzbdrone.db Edited September 11, 2020 by jang430 additional information Quote Link to comment
jang430 Posted September 11, 2020 Author Share Posted September 11, 2020 Update: So it turns out the only time my cache doesn't have anything writing on it is when all docker containers are off. Even with Unifi controller on, it writes frequently. Same with Emby, etc. Currently, I have my nvme as my cache drive. Does this shorten my nvme life significantly? Or can it handle it? Quote Link to comment
jang430 Posted September 11, 2020 Author Share Posted September 11, 2020 I'll read through it. It's just that I never thought about this before. But now, while closely monitoring this, I saw it doesn't stop writing. Even with only 1 docker container up and running, I believe unifi controller. Quote Link to comment
trurl Posted September 11, 2020 Share Posted September 11, 2020 If you have docker.img on cache as recommended then it will be open even if no containers are running. You have to disable the docker service itself in Settings - Docker. Quote Link to comment
jang430 Posted September 11, 2020 Author Share Posted September 11, 2020 I actually remember when I had docker apps in hdd, it was much slower to boot, and oftentimes encounter problems, or thought I encountered problems due to slowness to boot. It's much more snappy in ssd. To be honest, I have to move my 1 TB NVME out of cache already, and use it as unassigned devices (dedicated for gaming only). What will I assign as my cache drive? Will it be another SSD? Or just another regular hard drive? If another SSD, does it have to be enterprise quality? Knowing what I experienced above, that there are a lot of writes? Or consumer ssd will be good enough? Quote Link to comment
jang430 Posted September 11, 2020 Author Share Posted September 11, 2020 10 minutes ago, trurl said: If you have docker.img on cache as recommended then it will be open even if no containers are running. You have to disable the docker service itself in Settings - Docker. Is this correct? Quote Link to comment
trurl Posted September 11, 2020 Share Posted September 11, 2020 3 hours ago, jang430 said: Is this correct? It is the correct place in Settings, but that screenshot shows docker service enabled. 4 hours ago, trurl said: You have to disable the docker service itself in Settings - Docker. Quote Link to comment
jang430 Posted September 12, 2020 Author Share Posted September 12, 2020 hi trurl, Indeed, I am using probably 8 apps. I need docker service on. Is it accepted that once docker apps is on, it will keep on writing a lot to the cache? Quote Link to comment
trurl Posted September 12, 2020 Share Posted September 12, 2020 14 hours ago, jang430 said: I'll read through it. Have you had a chance yet? Long story short, there have been some changes in latest beta to address this. Quote Link to comment
jang430 Posted September 12, 2020 Author Share Posted September 12, 2020 It's a very long thread, and don't know if we exactly have the same problem. So this issue has been addressed in 6.9.0-beta25? I've stayed with 6.8.3 so far. But will go beta if it's fixed there. Don't want my cache dying on me. Quote Link to comment
SeeGee Posted September 12, 2020 Share Posted September 12, 2020 (edited) 15 hours ago, jang430 said: while closely monitoring this, I saw it doesn't stop writing. How much is being written? Is it a few bytes, or lots of megs? I'm running beta25, with raid1 ssd pool as well as raid1 nvme pool and I do get frequent writes, it's only a few k (docker runs on nvme pool) . Well within what I expect considering how many containers I have running. Edited September 12, 2020 by SeeGee Quote Link to comment
jang430 Posted September 12, 2020 Author Share Posted September 12, 2020 I haven't really bothered with the file size. I think it's not a lot as I don't notice drastic drop in my storage space. More issue is the amount of read and writes. In 36 hours, Reads of 1,123,531 and Writes of 2,337,765. Quote Link to comment
SeeGee Posted September 12, 2020 Share Posted September 12, 2020 With ssd's the only thing that really affects life expectancy is the AMOUNT of data written. For instance my particular nvme drives are rated at 640 terabytes written. If it's a few k per second, would take many years to get to that threshold. I'd have to write 350+ gigs to it per day and it would still take longer than the 5 year warranty before it becomes a problem. Quote Link to comment
jang430 Posted September 12, 2020 Author Share Posted September 12, 2020 Thanks SeeGee for the clarification. I thought amount of writes also determine lifespan of ssd. Quote Link to comment
Recommended Posts
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.