September 22, 20178 yr I'm not sure if this is related to 6.4, but it's the only thing I've run on my new server. The mover is ignoring the split level I've set on my user shares. I like to keep all seasons for each tv show all on the same disk, so I set it to split only the top level directory. The folder structure is tv/showname/season, so it should be free to place tv on any disk but keep everything related to a specific show on the same disk. However, it just moves everything to disk1, even though the show being moved has a folder on disk3 (and disk3 even has more free space than disk1). I configured the share settings exactly as I did on my old server running 6.3 where it worked like it should, so I'm not sure whats going wrong.
September 22, 20178 yr 41 minutes ago, hallifallen said: even though the show being moved has a folder on disk3 Do you mean this already exists before starting mover? /mnt/disk3/tv/showname/ If so, does this also already exist? /mnt/disk1/tv/showname/
September 22, 20178 yr Author 1 hour ago, limetech said: Do you mean this already exists before starting mover? /mnt/disk3/tv/showname/ If so, does this also already exist? /mnt/disk1/tv/showname/ Folder already exists on disk3 but not on disk1. And it's the same with shows on disk2, it just dumps it on disk1.
September 22, 20178 yr With High Water Allocation method disk1 will be used until the free space is down to the next Point for switching disks. Read up on the method for more detail on how it works. Edited September 22, 20178 yr by itimpi
September 22, 20178 yr With three disks of equal size and if you want all disks to be filled in an equal way, the better setting to use for Allocation method is "Most-free".
September 22, 20178 yr Here's how highwater works. Assume we start with 3x 10TB empty drives, disk1-3. Highwater is computed by taking the size of the largest disk and dividing by 2. Hence first highwater mark is 5TB. Data will be moved to disk1 until free space is below 5TB on disk1. Data will then move to disk2 until it's free space is below 5TB. Finally data moved to disk3 until it's free space is below 5TB. Now since there remains no disk with free space greater than 5TB we compute a new highwater mark by dividing by 2 again: 2.5TB Data starts moving to disk1 now until free space there is below 2.5TB. Then disk2. Then disk3. Next highwater mark: 1.25TB. This is where you are at. Data will continue to move to disk1 until free space there falls below 1.25TB.
September 22, 20178 yr And Most Free isn't really a better idea in most cases. If you get all your disks with about the same amount free, then it will constantly switch between disks when writing the share as it chooses the new most free. High-water is the default because it is a good compromise between distributing your data without constantly switching disks.
September 22, 20178 yr 2 minutes ago, trurl said: And Most Free isn't really a better idea in most cases. If you get all your disks with about the same amount free, then it will constantly switch between disks when writing the share as it chooses the new most free. +1 In my experience most free results in considerably slower writes because there will be overlapping writes to the parity disk.
September 22, 20178 yr Author Yes, I realize that's how highwater works. But it doesn't matter which allocation method the share is set to use, it never splits correctly as it did on my old server. If I have tv/Friends/ on cache, the tv share set to split only the top level, disk2 already has tv/Friends/, it shouldn't put /Friends in the tv folder on disk1, right? I just tested it with split set to manual, then it moves /Friends and the subfolders and files to the correct location on disk2. However, it also creates an empty folder named Friends in the tv folder on disk1...
September 22, 20178 yr 40 minutes ago, hallifallen said: If I have tv/Friends/ on cache, the tv share set to split only the top level, disk2 already has tv/Friends/, it shouldn't put /Friends in the tv folder on disk1, right? Yes that is correct, I think there is an issue. Testing...
September 24, 20178 yr Author Another issue with the mover. Gives me the following error (even though it has been moving files in the same mover session without issue). A restart fixes it and the files will get moved, but the next time the mover starts it will give the same error when moving some other files. Sep 24 14:42:19 batman shfs: err: assign_target: No space left on device (28): assign_disk: tv/Luther/Season 04/Luther - 4x01 1080p - Episode 1.mkv Sep 24 14:42:19 batman shfs: err: move_object: No space left on device (28): assign_target: 1 /mnt/cache/tv/Luther/Season 04/Luther - 4x01 1080p - Episode 1.mkv
September 24, 20178 yr 3 hours ago, hallifallen said: Another issue with the mover. Gives me the following error (even though it has been moving files in the same mover session without issue). A restart fixes it and the files will get moved, but the next time the mover starts it will give the same error when moving some other files. Sep 24 14:42:19 batman shfs: err: assign_target: No space left on device (28): assign_disk: tv/Luther/Season 04/Luther - 4x01 1080p - Episode 1.mkv Sep 24 14:42:19 batman shfs: err: move_object: No space left on device (28): assign_target: 1 /mnt/cache/tv/Luther/Season 04/Luther - 4x01 1080p - Episode 1.mkv This is being caused by same bug.
Archived
This topic is now archived and is closed to further replies.