So I have a 120gig SSD cache drive and plenty of storage on the array.  I noticed I was nearing capacity on the Cache drive for some reason out of the blue.

I looked at the content and a share on it that shouldn't reside on the cache drive.

 

I verified that the Share in question is set to not use a cache disk.

 

Any ideas what happened?  I honestly don't think I changed anything that I'm aware of.

I did have an issue awhile back where I had the cache drive fill up and since the mover stopped working for a little bit.  I thought I had fixed it, but I've not seen it run in awhile now manually.

 

Not sure if the two are related or not.

Could be the old problem...I"ve had cases where the Cache drive would fill up completely before the MOVER ran.

Different OS (mac and windows) seem to react differently to this, but they will both leave 'trash' files around on the cache drive.

I think when the mover runs, its then not sure if the trash reflects something that is still happening because of the OS, and consequently doesn't move the files (or delete them).

 

You might try:

1. Copy all the CACHE files from cache back to your PC.

2. Wipe out the CACHE files on the CACHE drive using MC. (be sure to delete hidden files, 'dot' files, etc.)

(if you have APP folders on the Cache (PLEX, etc.) you can leave those alone.

3. Now that cache is 'clean', move the files from your PC back again to Cache.  (BE SURE TO NOT EXCEED CACHE SIZE LIMIT as you copy)

4. Run the mover and see how it goes.

 

You are correct, the cache drive did fill up before the mover ran, actually I think I had a rogue download that just exceeded the cache drive.  The thing I don't understand is if it filled up I could see it flaking out, downloads stopping and apps fail to function, etc, but not really what occurred.  It's almost as if the mover moved it to a legitimate share only for some reason that legitimate share now exists on my Cache drive as well (which it shouldn't have).

 

The cache does have my apps on it like you said.

 

Any reason why I couldn't just copy the files on the cache share to the actual array?  Rather than to my PC?  I would assume I would get the same results there.

 

Anything special I need to do to make sure my mover script is working as intended again?

I know that bug exists with the GUI where the time changes if you run it manually, but I was aware of that and made sure the schedule was still set correctly.

 

The other thing is since that occurred it seems like CP doesn't even show up now, I've not really looked into this all that much though yet.  I'm more concerned with just the array functioning properly first

I don't see any reason you can't copy from CACHE directly to the ARRAY.

Just use 'disk shares' instead of user shares.

Be aware of folder structures...(a user share has a top level folder on each physical disk that it uses.)

 

Once you've copied from CACHE to the ARRAY, then you can delete the old files on the Cache.

There may be some permission flags and/or invisible files lurking on the Cache, so you might want to use Midnight Commander to delete those.

 

Thanks, I went ahead and went that route, all seems to be fine currently.

Just need to make sure the mover works this evening.

I'm having this issue, however it was because I did have the cache drive in one of my user shares included disk list. I copied and then deleted the files from the cache drive, then removed it from the included disks list, but when i moved them back and tried to run the mover the server just straight crashed.

 

Any ideas on what might be causing this? The cache drive is not full, and these are not duplicate files on the data disks. I'm getting some "rsync" error in the log btw.

I'm having this issue, however it was because I did have the cache drive in one of my user shares included disk list. I copied and then deleted the files from the cache drive, then removed it from the included disks list, but when i moved them back and tried to run the mover the server just straight crashed.

 

Any ideas on what might be causing this? The cache drive is not full, and these are not duplicate files on the data disks. I'm getting some "rsync" error in the log btw.

 

You'd get a better response by including your logs.

 

Sent from a mobile device, sorry for any typos.

 

 

I'm having this issue, however it was because I did have the cache drive in one of my user shares included disk list. I copied and then deleted the files from the cache drive, then removed it from the included disks list, but when i moved them back and tried to run the mover the server just straight crashed.

 

Any ideas on what might be causing this? The cache drive is not full, and these are not duplicate files on the data disks. I'm getting some "rsync" error in the log btw.

I'd start a new thread. It sounds like you've got a slightly different problem.  Add a reference link back to this post if you like.

 

SYSLOG:

http://lime-technology.com/forum/index.php?topic=9880.0

 

I was half way through writing a response about the mover script moving data from the completed directory of Sabnz to the share, but created that share back on the Cache drive instead of using the existing on the array drives.

 

However, I manually ran the mover and it removed those temp share from the cache.

 

I guess I just never realized that there was a temp share on the cache outside of the sabnz directory.

 

So I think I'm good now

I guess I'm just not sure if the scheduling is working for the mover.  I'll wait and see again to see what happens tonight.

I'm having this issue, however it was because I did have the cache drive in one of my user shares included disk list. I copied and then deleted the files from the cache drive, then removed it from the included disks list, but when i moved them back and tried to run the mover the server just straight crashed.

 

Any ideas on what might be causing this? The cache drive is not full, and these are not duplicate files on the data disks. I'm getting some "rsync" error in the log btw.

Are you saying that instead of setting the share to Use cache disk: Yes, you actually put the cache disk in the included disks for the share?

No, the cache disk is not part of the array disks, it wouldn't exactly be a cache disk at that point, it'd just be another array disk.

So I have several shares that are set to NOT use the cache disk ever.

Then my apps share is set to ONLY use the cache disk.

 

I have sabnz as an app.  I used to think that when a download completed it was just held in the completed folder of the sabnz directory, then when the mover script ran, it would relocate the content to the proper on array-off cache share.  What I think it's doing (and I could be wrong, but I'm not sure yet) is that sabnz when complete rather than using the completed directory it's using the root directory followed by the proper share name.

 

I don't think it's the mover script that's actually moving the completed movie to the root of the cache disk the more I think about it.

I've actually confirmed that it's a sabnz problem.  Again I'm not sure why, because it was working properly before the drive filled up.  But sabnz is dumping the temp directory into the root rather than using it's completed folder for the temp directory.

 

When I get home from work I'll have to see if the schedule for the mover is running or not, the manual run of the mover script seems to still move all the data properly, it's just that temp location isn't the right location.