March 26, 20197 yr I've got a weird that happens every night. Cache seems to get close to the edge and then back to normal in a matter of a few mins. Normally she looks like this: To what stupidity am I subjecting myself? limnas-diagnostics-20190326-1900.zip Edited March 28, 20197 yr by techsperion
March 27, 20197 yr Author So it looks like it's the Mover as it's shceduled for that time: But why is it filling up the drive ?
March 27, 20197 yr Enable mover logging in settings schedule and itll log what its logging and you'll see in the syslogSent via telekinesis
March 27, 20197 yr Community Expert Your share settings look fine. One share (other than the usual) named M--O is set to prefer cache but it is all on cache so it isn't clear why anything would be getting moved to cache. Or did you change some of your share Use cache settings after those notifications?
March 28, 20197 yr Author Thanks guys! Found the culprit thanks to @Squid suggestion to turn on mover logs. Created a VDISK of 500GB for one of my VMs to use. It's sitting on the domains share which is set to Prefer. So every night it was trying to move this large vdisk to a 240GB Cache and failing. Think I'm going to have to move its location off domains.
March 28, 20197 yr 1 hour ago, techsperion said: Thanks guys! Found the culprit thanks to @Squid suggestion to turn on mover logs. Created a VDISK of 500GB for one of my VMs to use. It's sitting on the domains share which is set to Prefer. So every night it was trying to move this large vdisk to a 240GB Cache and failing. Think I'm going to have to move its location off domains. Change domains to cache only or cache no, depending on whether you want new files created in the domain share to be on the cache or the array. I have this exact configuration, where some of the domain contents live on the array, some on cache. Fix common problems will complain, but that's ok if you do it on purpose and know what you did, you can just ignore the complaint.
February 25, 20206 yr Thanks for sharing the issue & fix. I too was getting the cache-fill each time the mover ran, and after you mentioned looking into the /mnt/user/domains, I found a older VM which I had removed but not deleted (was was larger than usable cache).
Archived
This topic is now archived and is closed to further replies.