My cache drive was working fine, if I copied data to the unraid, it would move it to the main drives at 3:40am everyday.  Furthermore, I could go to the Shares tab and click on the Move Now button and it would move the data right away.  After hitting the refresh, you would see the free space increase each time.  However, I was copiing data to my unraid and I got a message saying it was out of space.  I logged in and see that the cache drive is full.  I left it like that for a few days, thinking when I returned it would be ok, but NOT.  The cache drive is still full and nothing happens when I hit the Move Now button.  I have lots of free space on several other drives, so I don't get it.  I rebooted and checked the logs, no errors and everything looks fine.  Except the code that tells it to move the data to main drives is not working.  Anyone else have this issue?  I'm running 4.4.2, with Bubbaraid.  My system has been up and running for several months with no issues and I have not Smart data errors and no access issues.

 

Help!

In looking at the syslog, I'm getting a No space left on device error when the mover trys to run.  Here is an example of the syslog entry,

Aug 19 06:01:41 Tower logger: mv: writing `/mnt/user0/./movies/Comedy/National Lampoon\'s Vacation (1983)/NATIONAL_LAMPOONS_VACATION.ISO': No space left on device

 

I don't understand why.  I have a total of about 2tb free.  That share is set to split level 1, although I even had it on split level 2, no help, and on high water.

 

More screen shots attached.

 

Any ideas on what is going on?

 

 

A share split level of 1 would allow a new file (or folder) to be created in

/movies

A share split level of 2 would allow a new file (or folder) to be created in

/movies/Comedy

 

You are trying to create a new file in

/movies/Comedy/National Lampoon\'s Vacation (1983)/

 

The first step in "mover" creates and directories that do not yet exist.  I'm guessing when you started there was enough space on disk1 for the new directory at level 2, since a directory only takes a few bytes.  It was created just fine on disk1 based on your split level of 2.

 

Now that it exists, that folder (National Lampoon\'s Vacation (1983)) is therefore at a split level of 3.  Any files you attempt to create in it in it will not be created on another disk. They must stay on the same disk as the folder because you have the split level at 1 or 2.

 

Now, the file move is attempted... assuming that the directory already exists on disk1, there is no space left on that disk to copy the file BUT... you have forced it to stay on the disk with the folder by using a split level of 1 or 2. Hence the no space error.  You've forced files in that folder to stay on disk1, and according to the screen-shot... it is completely full.

 

Try split level of 3 or 4.

 

Joe L.

Thanks Joe, that was it.  I thought I understood the split level stuff, but I now see what you are talking about.  I changed it to sl 3 and that helped, moved about half off of the cache drive before running out of space again.  I had to change it to sl 4 and that solved the issue.

 

Thanks again!

Weird... I had an issue that was/is similar..

 

I'm running on a full slackware install with parity + cache. I got the disk full message even though there was plenty of free space.

 

The shortish story: I was visually watching files disappear after unzipping them.. I had no idea where they went until my root partition was full (100%!). All the missing files ended up in the black hole of /mnt/user0/<folders>. Each of the shares that had the issue were set to high-water with no split level anything.

 

Ive now switched these back to 'most-free' and will see how it goes.

thatis weird.  My issue turned out to be a split level lession for sure.  My problem didn't go away until I increased my split level to 6 on my shares.  They were set to 1 and 2 and each of the shares filled a physical drive full.  I don't have any problem now and I guess I really don't care that my data is spread all of the 8 drives.  After doing this I did run the Parity Check again to be sure all was good.

 

Good luck.

 

Steve

I've currently got my split level on my movies share set to 6 as well, but I'm storing my DVD rips on there in VIDEO_TS format, and a single movie can get spread around several drives, causing the system to have to spin up multiple disks as a movie plays.  This causes the system to pause until the drive comes up (is there ANY way to fix that?).  When I get the extra drivespace & time, I'm going to at the very least set up a seperate share for my DVD's, and manage the allocation myself (put the movies intact on a single drive, using the individual disk shares).  Might save me some WAF hits if it doesn't stop and then rapidly catch up on movies we watch...

 

Weird... I had an issue that was/is similar..

 

I'm running on a full slackware install with parity + cache. I got the disk full message even though there was plenty of free space.

 

The shortish story: I was visually watching files disappear after unzipping them.. I had no idea where they went until my root partition was full (100%!). All the missing files ended up in the black hole of /mnt/user0/<folders>. Each of the shares that had the issue were set to high-water with no split level anything.

 

Ive now switched these back to 'most-free' and will see how it goes.

 

 

I think I just found another cause behind this... When I pressed 'stop' to stop the array, the cache mover was still moving files to disk8. As it couldn't 'unmount' the folder of /mnt/user0 im guessing that upon reboot it won't re-mount it.

 

This would cause my /mnt/user0 to fill up quickly - in this case, it's an actual drive and not my flash drive.