November 8, 201411 yr Hi All, I am experiencing a problem that for the life of me I cannot fix. Here is my setup for context: 3x 3TB array drives (disk 1 = 100GB free, disk 2 = 700GB free, disk 3 1.2TB free) 1x 3TB cache drive (sat with 1TB of data needed to be copied to the array) 1x 3TB parity drive (parity valid) specific share setting share (x1) = media allocation method = high water split level = 6 included disks = disk1,disk2,disk3 use cache disk = yes min free space = 30000000 general share setting included disks (share settings) = disk1,disk2,disk3 use cache disk = yes min free space = 35000000 Some time ago I had an issue whereby disk 1 got full and then I got write errors when the mover tried to copy to the array at night and basically my cache drive never got emptied. I realised that the issue was down to the split level I had (level 4) and that I had inadvertently created a new level when playing with my structure. e.g. went from media>Movies>Movie to media>Movies>HD Movies>Movie So i stepped in now, and moved a hundred or so gig over to disk 2. This left things a bit uneven (disk 1 = 100GB free, disk 2 = 700GB free and disk 3 = 1.2TB free) but I could live with it. Basically I think know it meant when the mover kicked in, it tried to copy files to disk 1 because of the split level settings overriding allocation method and minimum free space setting. So, I changed the split level to 6 (which is high enough basically to disable it as my structure doesn't go down that far) which I thought would allow the folder to disk link to break and other disks to start being used. BUT it didn't. When I run the mover manually it continues to fill disk 1. So .... I changed the allocation method to Most free, thinking it would have to start using disk 2 or disk 3. I assumed disk 3 as it is the one with the most free space. I started the mover again - nope - continues to try and fill disk 1. I am lost! I don't know what to do. I am sure this is my fault but I cannot see where! I would appreciate any insight people have as I am literally sat here typing this and watching the mover continue to fill disk 1 and leave the others alone! (((
November 8, 201411 yr Author http://lime-technology.com/forum/index.php?topic=26511.msg318671#msg318671 [quote author=Nokoff link=topic=26511.msg318671#msg318671 date=1406123310] I'm getting mover errors i believe to be related to split level setting forcing the files to certain disks... rsync: write failed on "/mnt/user0/Series/The Mentalist/Season 06/The Mentalist - S06E02 - Black-Winged Redbird SDTV-thumb.jpg": No space left on device (28) rsync error: error in file IO (code 11) at receiver.c(389) [receiver=3.1.0] ./Series/The Mentalist/Season 06/The Mentalist - S06E01 - The Desert Rose SDTV.mp4 >f.stpog... Series/The Mentalist/Season 06/The Mentalist - S06E01 - The Desert Rose SDTV.mp4 ^Z [1]+ Stopped mover Nokoff in the thread above seems to have the same issue as me but doesn't post how it was resolved. Seems to be pointing towards my split level settings but I can't see how that can be given it is now 6. Unless .... Given when I first did the setup it was set to SL 4 and now irrespective of what I changed that folder is now linked to that disk!? Not sure what I am saying - sort of grasping at straws.
November 8, 201411 yr Not sure what your problem is - from your description things should work OK. Some observations: I would tend to leave the 'included disk' settings blank unless you really need them. The default is all disks. Unless you have disk present you do NOT want to be used for shares the global setting is irrelevant. Setting them when not needed is just likely to lead to errors later if you add another disk and forget they are set so forget to update them. You should be able to change the split-level and allocation method settings at any point. They only apply to new files and not to files already on the array (which are found for read purposes regardless of the share settings). Check that the problem files do not already exist on disk1. If they do then mover will always try and overwrite them rather than switch to using a different disk.
November 8, 201411 yr Author Not sure what your problem is - from your description things should work OK. Some observations: I would tend to leave the 'included disk' settings blank unless you really need them. The default is all disks. Unless you have disk present you do NOT want to be used for shares the global setting is irrelevant. Setting them when not needed is just likely to lead to errors later if you add another disk and forget they are set so forget to update them. You should be able to change the split-level and allocation method settings at any point. They only apply to new files and not to files already on the array (which are found for read purposes regardless of the share settings). Check that the problem files do not already exist on disk1. If they do then mover will always try and overwrite them rather than switch to using a different disk. Thank you very much itimpi. When I was writing the post yesterday i let the mover do its thing and move the files in the cache drive to disk1. I saw your post before I went to bed and changed my settings back as per your suggestions and changed the split level back to HighWater. Last night the mover did its thing and moved files, this time it chose disk3 (the one with the most free space). All I can imagine is that for whatever reason the files on the Cache disk already existed on disk1 which is why it kept choosing that disk to overwrite. I can think of a number of scenarios for that (especially if I was playing at the time). Anyway, problem seems to be solved. I shall monitor, things but it seems all is ok. Thank you once again.
Archived
This topic is now archived and is closed to further replies.