January 19, 201016 yr Hey gang. I have 1.5TB as Parity, 500GB as cache. 2x 1.5TB, 4x 750GB and 4x 1TB for data. I configured the share as 1 giant Vault share \\tower\vault\HD\Movies\Action (so on) \\tower\vault\AVI\movies or \Animated or \tv\frasier\season1 (so on) \\tower\vault\pictures so on.... I enabled the share as "Vault" with high water, split level set to zero, I left included disks blank as to have all disks listed above to be included (I want one giant array with one giant share and organize data within the one share), with cache drive enabled on this share and user permissions. Everything is cool and accessible. I watched a flick streaming HD while copying, not performance lags, very happy with performance I have 4.6TB of data to unload to this array. unloaded 697 GB starting lastnight and finished today successfully. When I started to copy 500 GB more to continue on, I got a disk full error. I noticed the cache drive was full and did not copy over lastnight at 3: something (I have it set to default). Did it not commit at 3ish am because the whole copy process of the 697 GB was not completed? If the cache drive is full and not committed, it wont let anymore data copy until it commits whats on there? If so, should I disable the cache drive from the share until all data is brought over?? I included a screen shot, for my own OCD, can someone just verify I set the share OK using high water? Thanks so much guys!!!
January 19, 201016 yr You can always force a move and/or just schedule them to run more often. As you stated, it might be wise to disable the cache drive while you're moving so much data. I have a 250G cache on my machine and I get nervous when I put more than 100G on it - it's gets hot when I run it hard. unmenu (found here in the forums) is a great way to get a better view of the status of your disk space (it actually shows available space in human-ish numbers).
January 19, 201016 yr Author WHOLLY!!! How ya doin?...I've come quite a bit since ya helped me last...huh? huh? Thanks for the response. I wish I could just have a 1TB cache drive for the big data migration! lol!! Does the way I set the share look right for the giant share I am trying to accomplish? I got nervous with the minimum size setting and leaving the "disks included" blank, does mean that all drives will be used for high water? Thanks again man. Good to know guys like you are out there.
January 19, 201016 yr Author Can someone give me a thumbs up on the screenshots of how my share is setup? Just want to make sure the minimum drive space and the designated disks field being blank to include all disks is cool. Thanks!!
January 19, 201016 yr I'd recommend just turning it off for the big move. Although the transfer won't be as fast, you won't have to do it in chunks. Looking at your share config, it seems that Vault has a minimum of 15.7G That should keep you from breaking a bluray rip (assuming you're getting them under 15g...) I also note that your cache move is only scheduled for once per day at 3:40 in the morning. That's probably not often enough if you're looking to put 4T out there in 24hours or so. Once again, I'd recommend turning it off for the big move as you only get data protection when it's copied to the array. I'm glad to see that you're getting some serious stuff going!
January 19, 201016 yr Author Thanks again Wolly. Appreciate the help. I commited the cache drive data, then removed the cache drive from the share option. I'm back to moving data again. My next question to anyone out there is in regards to high water, I went through the wiki (again) and I think its not performing correctly. The data is being copied to my one of my 1.5TB drives, and that drive is now 77% full and none of the other drives have been touched yet? Any ideas? Thanks to all again!!!! (I feel like I'm ALMOST there) lol
January 19, 201016 yr I think the issue is your split level of "0" See here: http://lime-technology.com/forum/index.php?topic=3760.0
January 19, 201016 yr Author Thanks Joe L!! So from what I read from your link, will the split 0 method then move onto the next disk when this disk is full?? The link you sent me stated "according to the allocation method used" I though it might just still do its thing with High water. My question then is, (for ex.) if disks 1 through 12 are included in my "Vault" share, as well as split level 0 being used, using the share from a Windows machine, I create... \\tower\vault\movies.... then I get... \\tower\vault\movies on DISK 1 (which I do, the rest of the disks have nothing)... When disk one fills, it will then create.... \\tower\vault \movies on disk 2? That would seem like the fill up method, did I do something wrong, do I have a grip on the theory? I have no probs if it does react this way, thats fine...at least I can understand whats going on and how it works and I can say I learned something. I just don't want to fill my first of 12 disks, and then when its time to go onto the next disk while migrating 4.6TB of data, it will give me a disk full error because for some reason it didn't traverse over to another disk. I feel like I understand, I just want to be re-assured, especially for learning purposes, how the allocation behavior will act using this method. Thanks guys!!! (Al...most....GOTIT!!) lol
January 19, 201016 yr Thanks Joe L!! So from what I read from your link, will the split 0 method then move onto the next disk when this disk is full?? No, not unless YOU create the same folder there as on the first disk.The link you sent me stated "according to the allocation method used" I though it might just still do its thing with High water. My question then is, (for ex.) if disks 1 through 12 are included in my "Vault" share, as well as split level 0 being used, using the share from a Windows machine, I create... \\tower\vault\movies.... then I get... \\tower\vault\movies on DISK 1 (which I do, the rest of the disks have nothing)... When disk one fills, it will then create.... \\tower\vault \movies on disk 2? no, it will NOT create a folder on disk2. If you want it to do that automatically, you'll need to set the split level at "1" so the first (top level) directory can be "split" across the disks. That would seem like the fill up method, did I do something wrong, do I have a grip on the theory? I have no probs if it does react this way, thats fine...at least I can understand whats going on and how it works and I can say I learned something. Hardly anybody as a grip on the theory. I don't use a cache disk, and I always only copy to the "disk" shares. My user-shares are used as read-only. I just don't want to fill my first of 12 disks, and then when its time to go onto the next disk while migrating 4.6TB of data, it will give me a disk full error because for some reason it didn't traverse over to another disk. I feel like I understand, I just want to be re-assured, especially for learning purposes, how the allocation behavior will act using this method. Thanks guys!!! (Al...most....GOTIT!!) lol If you wish the Vault directory to only be on some disks, you can create the folder on the disks you wish and leave a split level of "0" and it will only use those disks.
January 20, 201016 yr Author OMG I think I got!! I think Im just going to start over again. (joy) Just a few last questions (I hope) Would I have to copy just the vault folder to all the drives I would like used, or would I also have to replicate the directory structure exactly by also having to copy (Ex.) vault\movies\action (To all disks) vault\movies\drama (To all disks) vault\tv\simp\season1 (To all disks) vault\tv\simp\season2 (To all disks) Or just "Vault" folder which would be the root of all these? If I set it for example to split method 2, would it only automatically copy up to.....vault\tv\simp but not \season1? So that if I wanted season 1 and season 2 (etc) folders I would have to set to split level 3? Im going to also follow your lead and ditch the cache and just use as storage instead. Man, this is a great "newbie" thread for all newbies to come....
January 20, 201016 yr OMG I think I got!! I think Im just going to start over again. (joy) Just a few last questions (I hope) Would I have to copy just the vault folder to all the drives I would like used, or would I also have to replicate the directory structure exactly by also having to copy (Ex.) vault\movies\action (To all disks) vault\movies\drama (To all disks) vault\tv\simp\season1 (To all disks) vault\tv\simp\season2 (To all disks) Or just "Vault" folder which would be the root of all these? You would need to create the sub-directories. It will not if you have the split level set to 1. If I set it for example to split method 2, would it only automatically copy up to.....vault\tv\simp but not \season1? So that if I wanted season 1 and season 2 (etc) folders I would have to set to split level 3? You've got it. You would need a split level of 3. Im going to also follow your lead and ditch the cache and just use as storage instead. The "cache" drive only makes sense if you need to write to the server at a rate faster than otherwise possible to the protected array. (Recording .ts stream from an HDTV tuner is one such high-speed need, although recent improvements might even be able to keep up with it. ) It ONLY works if the cache drive is able to hold all you will transfer in a given day (or until you move the data manually instead of waiting for the default 3:40 AM scheduled move.) When transferring more data then it will hold, it will only get in the way. My biggest data transfers are when I rip a new DVD to the server. I don't care if it takes 15 minutes, or 30 minutes... or 5 minutes... The use of the cache drive would not do anything for me. Man, this is a great "newbie" thread for all newbies to come.... Hope it helps... Joe L.
January 20, 201016 yr The release notes for 4.5 say "- Special handling of split level explictly set to "0"." I think I recall reading something about the 0 was set back to mean split however with no limits. Personally, I would start with using "2". This means your "Vault" directory can go on every disk and any subdirectories under "Vault" can go on every disk. But anything below that is fixed to the disk it's created on. For example, \\Tower\Vault\Movies can exist on every disk. However, any directory you put under "Movies" such as the directory "Action" is locked to the disk it is first created on. If you allow unlimited split level then you can get fragmentation of the data. For example, you might have a directory in your Movies named "Terminator". Under that directory you have the movie file and images and a media info file. Allowing an unlimited split level means that each of those files could end up on a seperate disk. Honestly, I would reconsider the combined share. Maybe 3 (or more) - "Movies", "TV Shows", "Music" Peter
Archived
This topic is now archived and is closed to further replies.