February 17, 201214 yr I only recently stumbled upon the "Avoid filling drives >99%" entry in the Wiki, but has impacted me greatly. I used to get a ~45 second delay sometimes while browsing my unRAID servers via my Win 7 desktop. After redistributing some data to keep all my drives <99%, I can now navigate them much quicker. With this in mind I was thinking how it would be nice if we could mark a drive as full and no longer write to that drive via user shares so as to avoid filling it above 99% and incurring the potential slowdown. I would think you could still allow writes to the disk so as to allow an easy manual override. I'd like to just mark a drive and know that Sick Beard will no longer write anything to that disk while writing to my "TV" share. On a side note; why is the only Feature Request forum for 4.x and closed? I would think that a FR forum should always be open and available. Not a biggie. I never thought about it or looked for it before, but I found it a bit odd there was no open FR forum/thread.
February 17, 201214 yr Author I didn't realize that was per disk. Stupid I guess, but I thought that was overall. Still, it would still be much easier to simply mark a disk and it be be excluded from all share writes rather than have to go through each share and set the minimum free space. Not to mention that that could sometimes change, too. If a disk is full, it's full. This should be a disk level option, not share level.
February 17, 201214 yr Author I just thought of another reason why the min free space setting is probably not the best option for what I'm wanting to do. You can only set a single value, but if you have varying sizes of disks, this would cause a problem. For example, my smallest drive is 500GB and my largest is 2TB. To stay under 99%, but still fill the disk as much as possible (say 98% full), I would need to set free min space to ~10GB for the 500GB drive, but the 2TB drive would need to be set at ~41GB. If I set the min free space setting in the user share to 10GB, I over fill the 2TB drive and performance suffers. If I go with the 41GB setting, every drive stays under the magical 99% mark, but I end up with a fair amount of wasted space. For my total array I estimate I would waste ~175GB if I went with the 41GB setting. Again, I think this would be better as drive setting rather than a share setting. Feel free to point out if my thinking is flawed.
February 17, 201214 yr Just exclude the disk from the share when you don't want to fill it any further. Peter
February 17, 201214 yr Just exclude the disk from the share when you don't want to fill it any further. Peter This is what I do
February 17, 201214 yr I only recently stumbled upon the "Avoid filling drives >99%" entry in the Wiki, but has impacted me greatly. never knew that either. Can you post the link to which section of the Wiki had that?
February 17, 201214 yr never knew that either. Can you post the link to which section of the Wiki had that? End of the page. http://lime-technology.com/wiki/index.php?title=Improving_unRAID_Performance
February 17, 201214 yr never knew that either. Can you post the link to which section of the Wiki had that? End of the page. http://lime-technology.com/wiki/index.php?title=Improving_unRAID_Performance Thanks. Greatly appreciated. Will need to look at the entire page more closely to find out what else I've been doing wrong.
February 18, 201214 yr Author Just exclude the disk from the share when you don't want to fill it any further. Peter Thanks for pointing this out. I assumed that if I excluded a disk from a share then it's existing data would not show in the share either. I didn't realize that setting was for writes only. Seems like that should do the trick.
Archived
This topic is now archived and is closed to further replies.