May 2, 201313 yr Hi guys, I just realized the problem, still dont know why it exists. See, my split-level is set to 1. this results in 2 big folders on Disk 1, and 1 Big Folder in disk 2. both are part of my usershare. Now, I want to Add Files to The Folders, which are physically located on Disk1. I would expect unraid to write these to disk2 instead, because disk1 is full. Well, It does not. It just tells me there is not enough free space. Is this expected behaviour? now this is a curious one. I have a user share on my rc12a unRAID. I did not use my unraid for the past month. Today I upgraded to Pro, and when trying to copy files to my Folders inside my User share, I get a windows error, "there is not enough free space". It gets more curious: My user share is called "NAS". I can copy files to its root. But I can not copy files into the existing folders. I can make new folders, which work fine. In the existing Folders, I can create new text documents, but I can not write text inside them. I can rename stuff and create folders inside, but can not copy any files there. I hope this is understandable and someone can help me. THANKS! syslog.txt
May 2, 201313 yr Yes this is expected behaviour. With a Split Level of 1 then only the top level folder can be replicated across disks. This means that once a folder has been created on a disk any sub-folders or contained files are constrained to be on the same disk. It sounds as if to get the behaviour you are looking for you are going to require at least a split level of 2.
May 2, 201313 yr No - You need to do this manually. You would normally do it by copying the files between the disk shares rather than the user shares
May 2, 201313 yr is there an option to redistribute the files if one disk is full? Nope. Unraid will never move files off of a data disk. Only on to data disks from the cache drive, following all the disk allocation and split settings. Your best bet is to get familiar with the console command mc, which will provide a fairly easy way to move things around from disk to disk inside the array without moving things across the network. You also need to get comfortable with the disk allocation and split level settings so things work the way you want them from the beginning so you don't get into this situation again. If you are unwilling to learn new command line and mc stuff, you can always turn on the individual disk shares, and move things around using one of your network connected machines on the disk shares. Honestly, the way I use my unraid is to add stuff using the disk shares, so I know exactly what, where, and how much, then read them using the user shares so I see the whole collection at once. I'm a little anal retentive, and have my disks organized alphabetically, so for instance on the first disk that contains tv shows, I have only shows that start with A-E, the next one down has shows starting with F-L, etc. When my media player accesses the user share, it sees all the tv shows together, but I know exactly which disk holds what show. It's more work, but it makes me feel better. OCD is a bitch sometimes.
May 4, 201313 yr Author Hey that is some great advice! Maybe I should do it the same way, using disks to write and shares to read Thanks!
May 4, 201313 yr I do the same => copy to disk shares, but access via user shares. This lets YOU control the distribution of files on the disks ... and also control just how much you put on any given disk.
May 4, 201313 yr ... one other thought: You should also rethink your "split level" so if you DO copy to a user share, you won't have the issue you're having now. A split level of 1 is rarely the right choice.
May 5, 201313 yr I do the same => copy to disk shares, but access via user shares. This lets YOU control the distribution of files on the disks ... and also control just how much you put on any given disk. Me too. Never have to consider split level, high-water, etc. Tapatalk from CM10.1 Kindle
May 5, 201313 yr Have you noticed a difference since you changed split level to 2? Also, what is your allocation method?
Archived
This topic is now archived and is closed to further replies.