December 16, 200718 yr Perhaps I'm going about this the wrong. I'm sure I've pretty much done every combo I can think of. My Shares are Set using High-water split level 999. I have "Backups" on the root of Disk1 and 2. I have "Avi - Keep" on the root of Disk 3 and 4. I have "Avi - Burned" on the root of Disk3 and 4. (nothing in this share at all) "Shared 1" is high-water level 0 on disk1 "Shared 3" is high-water level 0 on disk3. Disk5 is a 320GB drive thats full. No shares on it (single encrypted file) All the others are 500GB each. Plus the Parity that is also a 500. That seemed to work. At some point I also had "Avi - Keep' on the root of disk2 as well. I just noticed that stuff keeps getting put back on disk2 when I copy files to the share "Avi - Keep" I can move the files back to my pc. Delete that dir from the root of disk2, restart the Server and it gets recreated on me when I copy data to the share "Avi - Keep". Nor does it seem to matter how I do this. I can disable user shares, start the raid, delete the dir on disk2, stop the raid, reenable the user shares, restart the raid. .... and again it recreates the root dir on disk2 and puts data there. Disk3 is pretty full. Disk4 is almost empty. Why is it even using disk2? I had thought that the dirs in the root of drives are what defines the user shares when the server is started. How is it remembering that disk2 once had this dir on it and how do I get rid of it. I want it to use the other 2 drives that have this dir on their roots. Nor does the exclude line seem to do anything. what is the format for filling this in? from the manual it would seem to be "disk1,disk2" with commas in there if needed but this did not seem to do anything. I tried putting "disk2" in the exclude line of the "Avi - Keep" share but it still wrote to disk2. So I just dropped something in my "Avi - Burned" share that has always been empty. Its never been on disk2. Yet a new dir just got created on Disk2 with the data I dropped into the share. What is going on? Why is unRAID creating root level dirs on other drives when I put something into a user share? Does this mean that if I'm putting data into the "Backups" share that fills up the first 2 drives that unRAID will create a root level dir on disk3 or 4 or even 5. Heres how much is currently free on each drive 1 = 136,502,588 2 = 283,781,080 3 = 25,018,524 4 = 486,902,656 5 = 8,139,504 drives 1,2,3,4 report total size as 488,386,552 and 5 is size 312,571,192 Have I completely misread how shares are defined? Are the dirs I personally make in the Roots only the starting points and unRAID will just start filling up drives until it reaches the high level mark and then move onto the next drive regardless of what user share I'm writing to. If this is the case, how to I use the include,exclude lines to change this. Programs using "Backups" run only run once in awhile very early in the morning, Those drives can stay spun down most of the time. The other stuff I thought I had defined for disk 3,4 can sometimes run more often depending on what I'm doing. Is this a result of using split level 999? I do want the processes to be free to write to either drive. I just want it limited to the 2 drives I thought each set of shares was using. What are your thoughts, comments, perhaps suggestions about a better way to think about it. I don't truly care what drives are being used. I had mainly set it up this way so that "backups" would have dedicated space and would thereby never run the risk of a failed backup in the middle of the night. If unRAID will grab space from any other drive that has free space when needed then thats a good thing. I just need to rethink the whys of how I had things set up.
Archived
This topic is now archived and is closed to further replies.