Something is writing to my cache drive, but all docker apps off, VM off


jang430

Recommended Posts

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 by jang430
additional information
Link to comment

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?  

 

 

Link to comment

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?

Link to comment
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 by SeeGee
Link to comment

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. 

Link to comment

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.

Guest
Reply to this topic...

×   Pasted as rich text.   Restore formatting

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.