Hi All,

 

First I would like to apologize. I have searched and searched, and I am just at a loss as to what is going on. For quite some time I have not had any issues with my unraid setup. I use a cache drive and the mover worked fine.

 

After a number of months, something happened, and the mover stopped working. I had to move everything manually. From then on nothing would copy to cache drive. I ended up turning off using the cache drive for a while. I recently re-enabled it through the global share settings. The drive filled up, and I am having the same issue again. I have adjusted min free space for my movie share, and maybe a couple other things that I can't think of. Mover is stuck running now. I can't stop the array, kill mover, and now get plex to work due to the cache drive being full I presume.

 

I don't know what else to check. I am at a loss and need your help. If I need to rebuild the system I am willing to as long as I don't lose any data. I can pull docker off the cache drive, and format the cache drive, whatever I need to do. 

 

I have attached current logs, hopefully they will prove to be useful.

 

Thanks!

unraid-diagnostics-20170809-1342.zip

This is the problem:

 

/dev/sdb1       224G  223G     0 100% /mnt/cache

Aug  9 13:36:09 UnRaid root: rsync: write failed on "/mnt/cache/Movies/Movies/Dolby Atmos Demonstration Disc (2014)/CERTIFICATE/BACKUP/id.bdmv": No space left on device (28)

But if manually moving stuff off of the cache drive doesn't help fix it, then you're going to need @johnnie.black's expert assistance, since it looks like you're running BTRFS on the cache drive (but no pool...  If no plans to ever run a pool, you may be better off using XFS.  Its more forgiving)

 

(And possibly related, either your docker.img or libvirt.img file has problems)

Aug  9 01:17:02 UnRaid kernel: BTRFS warning (device loop1): csum failed ino 48269 off 16384 csum 3062802139 expected csum 0

 

Here is another issue. Why would that be touched? It's been on my array for a long time. since.. well 2014. haha. It's like I have some setting and everything is trying to go to the cache drive? on my cache drive I see a bunch of movie folders. When there should only be new data on the cache drive, getting ready to be moved to the array with the mover script. It's almost like the data is going in the wrong direction? If that makes sense?

1 hour ago, hamish_18 said:

Here is another issue. Why would that be touched? It's been on my array for a long time. since.. well 2014. haha. It's like I have some setting and everything is trying to go to the cache drive? on my cache drive I see a bunch of movie folders. When there should only be new data on the cache drive, getting ready to be moved to the array with the mover script. It's almost like the data is going in the wrong direction? If that makes sense?

Do you have those user shares set to cache-prefer? That setting will move files from the array to cache. The correct setting for writing to cache then moving to array is cache-yes. See here: 

 

interesting. I totally read that wrong. I read prefer as it will use the cache until full and then the data will just go to the array. So if I am copying over more than what my cache drive's total size is before the mover script runs, then the data will start being written to the array. 

 

Will setting that setting to yes perform in this manner? I did just change it and transferred some data to the share, and it's being written to the cache drive like it's supposed to! the real test is whether the mover will work.

 

Thanks for the help so far. Hopefully this was all that was wrong.. Will report back after a couple more tests.

Looks like problem here is the wrong cache setting, libvirt.img needs to be recreated though if you want to use VMs in the future.

I think all I needed was to start this thread. I have pretty much everything the way I want it now. for the first time too I now saw my parity drive even spin down lol. Plex is running from the cache drive, and everything survived the array going down, reboots, etc.. 

 

Thanks for the quick responses! I think this can now be closed. And Johnnie.black. Thanks for the note, I will take care of libvirt. I plan on re-doing my whole vm setup once I get another ssd put in. I'll just have all the stuff like vm's appdata on my current cache ssd, and then use the new ssd as the sole cache drive. or however the best way to set it up will be. Haven't really looked in to that quite yet.

 

Thanks again!!!