malaki86 Posted February 11 Author Share Posted February 11 The new share, /mnt/user/media_Movies, exists on all eleven drives Quote Link to comment
malaki86 Posted February 11 Author Share Posted February 11 I just tried switching between High Water and Most Free for the new share. It's still writing to the drive with the least free space (and has well below the minimum free space). Quote Link to comment
itimpi Posted February 11 Share Posted February 11 7 minutes ago, malaki86 said: Dynamix File Manager plugin Do not know why you are not getting expected results then. Reason for asking for what you were using is that if you use Move from something like Krusader or 'mv' at the command line you can get files unexpectedly staying on the same disk because of the behaviour described in the Caution in this section of the online documentation. Dynamix File Manager implements move using a copy/delete strategy so should not suffer from this issue. Quote Link to comment
malaki86 Posted February 11 Author Share Posted February 11 Just now, itimpi said: Do not know why you are not getting expected results then. Reason for asking for what you were using is that if you use Move from something like Krusader or 'mv' at the command line you can get files unexpectedly staying on the same disk because of the behaviour described in the Caution in this section of the online documentation. Dynamix File Manager implements move using a copy/delete strategy so should not suffer from this issue. That's why I'm using the FM plugin. what about a direct rsync instead, or does the FM use rsync in the background already? Quote Link to comment
itimpi Posted February 11 Share Posted February 11 Just now, malaki86 said: or does the FM use rsync in the background already Yes. disk to disk moves will work as that explicitly places files but not sure why your user share to different user share is not working as expected. Quote Link to comment
malaki86 Posted February 11 Author Share Posted February 11 That's what's driving me insane. I just stopped the array. Hoping that spinning it back up might help? Quote Link to comment
itimpi Posted February 11 Share Posted February 11 1 hour ago, malaki86 said: That's what's driving me insane. I just stopped the array. Hoping that spinning it back up might help? It might be worth seeing if @JorgeB has an idea? I seem to remember that there is an ‘included disks’ bug that can perhaps be relevant, but I am not sure of the details. Quote Link to comment
malaki86 Posted February 11 Author Share Posted February 11 I emptied the cache 100%, stopped the array, changed the share from High Water back to Most Free, restarted the array same problem - it's writing to the full disk every time Quote Link to comment
trurl Posted February 11 Share Posted February 11 As mentioned, Split Level has precedence over Allocation. And if it didn't, Split Level would be meaningless. Just move from disk to disk, that gives you complete control over which disk a file is moved to. Quote Link to comment
malaki86 Posted February 11 Author Share Posted February 11 Okay - I thought I would try something. I have had the new share set to write directly to the array because of the volume of files that I have to move. So, for sh*ts & giggles, I changed the share to use the cache again. I selected about 10 movie folders with spread out files to move, which landed them in the cache, as it should. When that finished, I started the mover, and it starts by sending the files to the drive with the most free space. But, for whatever reason, it starts moving them to the empty drive, yet again... Quote Link to comment
malaki86 Posted February 11 Author Share Posted February 11 1 minute ago, trurl said: As mentioned, Split Level has precedence over Allocation. And if it didn't, Split Level would be meaningless. Just move from disk to disk, that gives you complete control over which disk a file is moved to. Then why is there even a split level option, being that is is meaningless? Serious question. It's easy to look and see "hmmm - there are 10.25Gb of files to move, but this drive only has 8Gb free. Let's look on the next drive." Quote Link to comment
malaki86 Posted February 11 Author Share Posted February 11 And, again, there are literally thousands of file to move. I *thought* that a built-in feature of the operating system I purchased would actually work correctly. Quote Link to comment
trurl Posted February 11 Share Posted February 11 The fact that Split Level has precedence over Allocation Method is exactly what makes it have meaning. 22 minutes ago, malaki86 said: started the mover, and it starts by sending the files to the drive with the most free space. But, for whatever reason, it starts moving them to the empty drive, yet again... Don't understand this part. Isn't that what you wanted, for cache to move them to the Most Free drive, which is the empty drive? In any case, mover is still going to respect Split Level, and if Split level says files belong together on another drive, it will override Allocation. Quote Link to comment
trurl Posted February 11 Share Posted February 11 One thing you could do when using cache and mover is to Exclude from the share any disk you don't want it to move to. Quote Link to comment
malaki86 Posted February 11 Author Share Posted February 11 (edited) 5 minutes ago, trurl said: The fact that Split Level has precedence over Allocation Method is exactly what makes it have meaning. Don't understand this part. Isn't that what you wanted, for cache to move them to the Most Free drive, which is the empty drive? In any case, mover is still going to respect Split Level, and if Split level says files belong together on another drive, it will override Allocation. I said that it STARTED to move the files to the drive with the most space, which is where they should be, not on the drive that is full beyond it's allocated space. There is ZERO reason that a 5Gb file, plus 2 32kb files can't be automatically be stored on a drive with 1.72Tb of space available, instead of "NO - PUT IT ON THE DRIVE WITH 50Mb FREE" Edited February 11 by malaki86 Quote Link to comment
malaki86 Posted February 11 Author Share Posted February 11 Did they think that no one would EVER fill up a hard drive when they did the whole split level thing? It also makes me wonder why I have the same new destination folder on every single drive in the array. By the whole "split level has precedence" thing, shouldn't that folder only exist on one physical drive? Quote Link to comment
trurl Posted February 11 Share Posted February 11 30 minutes ago, trurl said: Split Level has precedence over Allocation. And if it didn't, Split Level would be meaningless. I don't think you have understood this, since it seems to be what you are railing against. If Allocation Method had precedence over Split Level, it would always use Allocation Method to decide where to put a file, and so Split Level would be meaningless. How could it be otherwise? If Allocation Method had precedence, it would take a look at Allocation Method first, and since it gives a clear indication of where to put the file, there is no need to consult Split Level. Since Split Level has precedence, it takes a look at Split Level first, and since it give a clear indication of where to put the file, there is no need to consult Allocation Method. Quote Link to comment
malaki86 Posted February 11 Author Share Posted February 11 How could it be otherwise? By using a little logic prior to moving anything. Will it fit PROPERLY on this drive with all of the files? No? Ok, let's check the next drive. Quote Link to comment
trurl Posted February 11 Share Posted February 11 Another thing you could do to prevent it putting a file on the disk where split level says it should go, is to set Minimum Free for the share to a value larger than the file. Then it would just give you an error since the disk selected doesn't have Minimum Free. All of this works as logically as possible. If you don't want it to use Split Level to decide where to put a file, then don't set the share to use Split Level. Quote Link to comment
malaki86 Posted February 11 Author Share Posted February 11 Like the issue I'm having - the drive is well below the allocated space, regardless of the split level, it's STILL trying to put the files there, even though there are 10 more drives with MORE than enough space. It needs to look at EVERYTHING before moving - not just one item Quote Link to comment
malaki86 Posted February 11 Author Share Posted February 11 1 minute ago, trurl said: Another thing you could do to prevent it putting a file on the disk where split level says it should go, is to set Minimum Free for the share to a value larger than the file. Then it would just give you an error since the disk selected doesn't have Minimum Free. All of this works as logically as possible. If you don't want it to use Split Level to decide where to put a file, then don't set the share to use Split Level. I have a minimum free space of 200Gb. The largest file I've moved is 75Gb. Yesterday, it had the free space down to 85Kb, but was trying to put 10Gb files on it. Quote Link to comment
trurl Posted February 11 Share Posted February 11 1 minute ago, malaki86 said: How could it be otherwise? By using a little logic prior to moving anything. Will it fit PROPERLY on this drive with all of the files? No? Ok, let's check the next drive. In the general case of writing new files to a share, Unraid doesn't know in advance how large a file will become, so it chooses a drive for it in advance, based on Split Level, Minimum Free, and Allocation Method. Quote Link to comment
malaki86 Posted February 11 Author Share Posted February 11 These aren't NEW files - they're files sitting on the array on different drives. It knows how big they are, otherwise the File Manager wouldn't be able to calculate any kind of time estimate, could it? Quote Link to comment
trurl Posted February 11 Share Posted February 11 2 minutes ago, malaki86 said: I have a minimum free space of 200Gb. The largest file I've moved is 75Gb. Yesterday, it had the free space down to 85Kb, but was trying to put 10Gb files on it. Sorry, I misspoke. Split Level has precedence over Minimum Free also. I'm pretty sure the trick of Excluding the disk from the share would work though. It won't write new files to a disk that is excluded. All disks are still included for reading the share. Quote Link to comment
malaki86 Posted February 11 Author Share Posted February 11 that is nothing more than a temporary fix. Exclude one drive, it overfills the next, exclude that drive, it overfills the next. That's not a fix Quote Link to comment
Recommended Posts
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.