Title says it all, i have one drive that has 55GB left free, what happens when it fills up?

When it fills up, no more data can be written to it.

 

Sent from my A510 using Tapatalk HD

I have just been noticing that unRAID will get extremely slow when you try to add files to drives that have less than about 15GB free.  I have a 10 drive array (all 2TB drives) and over the last few months had been running low on space, during this time Windows 7 would take a long time "discovering files" when attempting to copy a new file to the array.  As the free space dropped to about the 12GB point it was eventually failing with a network error (after several minutes of waiting for the copy to start).  Nothing was reported in the unRAID syslog.  When I went to the unRAID console and tried a few copies I there I also encountered long delays - and commands that never finished.

 

Yesterday, as an experiment, I removed about 50GB from one of the drives and the slow copying problem went away.  This suggests to me that there is some sort of low disk space error condition that is getting masked at some level in the system and the result is a command that never completes (hence the network time out).

 

In the past few years I've always popped in a new drive long before this happened, but this year I was waiting for the 5.0 release version so I could transition to 4TB drives and ran out of space before the release happened.  So now I am upgrading to 5.0rc11 and preclearing a couple of new 4TB drives which I will replace my parity drive and one of the 2TB drives with to make space.

 

Regards,

 

Stephen

There is a known issue with ReaiserFS file systems (on all systems, not just unRAID) in that they start slowing down significantly for adding new files as they get very full.    I expect this is what you are seeing?

There is a known issue with ReaiserFS file systems (on all systems, not just unRAID) in that they start slowing down significantly for adding new files as they get very full.    I expect this is what you are seeing?

 

That could well be the cause. It's a good thing the problem seems to go away just by freeing up some space.

 

Stephen