October 31, 201411 yr My shares are already set up so that the split level is 1. I want to make it 0 and restrict one type of media per physical disk. So what will happen if I change the split level to 0 in the current state and /or change the included/ excluded disks to limit the share to a single disk?
October 31, 201411 yr My shares are already set up so that the split level is 1. I want to make it 0 and restrict one type of media per physical disk. So what will happen if I change the split level to 0 in the current state and /or change the included/ excluded disks to limit the share to a single disk? The change will apply to new files - existing files will be unaffected. When trying to browse files they will be found even if they are present on disks that are now excluded via the share settings for new files. If you want to do any re-organisation of the files to match the new settings then you need to do this manually by copying between the appropriate disk shares. WARNING: Do not mix disk shares and user shares when copying as this is likely to result in data loss.
October 31, 201411 yr Author What do you mean by mixing disk shares and user shares? As an example, I am planning to use midnight commander to copy from Movies folder on disk 2 to Movies folder on disk 1. Then delete the Movies folder on disk 2 and then make the change in share split level. You see anything wrong with that? Thanks!
October 31, 201411 yr As itimpi noted, it's very important that if you move any files around between disks as part of your reorganization you use the disk references, NOT the share references when doing those moves -- otherwise you can lose data !!! e.g. if you want to move some files with a share called "Music" that are currently on disk3 to disk2, do NOT move them from \\Tower\Music\<filename> to \\Tower\disk2\Music. Instead, move them from \\Tower\disk3\Music\<filename> to \\Tower\disk2\Music As already noted, changing the split level only impacts files you add after the change. All other files will remain where they are. And the Includes/Excludes only apply to writes -- when you reference a share, any disks that contain a top-level folder with the share name will be included in the merge. By the way, do NOT use both Includes or Excludes ... just use one or the other [if you have any Includes, then by default all other disks are excluded; and conversely if you have Excludes, then by default all other disks are included.]
October 31, 201411 yr ... copy from Movies folder on disk 2 to Movies folder on disk 1. That will work fine -- as I just noted, you do not want to use the Share reference for the moves, but as long as you're using the disk references you're fine.
October 31, 201411 yr FYI, this is the issue we're telling you to avoid: http://lime-technology.com/forum/index.php?topic=34480.0
October 31, 201411 yr A bit more r.e. the Includes/Excludes: As I noted, you should only use one of these. The key difference is what you want to happen when you add new disks to your array ... => If you only want shares to use the disks you've explicitly designated, then use Includes. But this means that when you add a new disk to the array, you have to explicitly add it to the Includes for any shares that are allowed to use it. => If you have specific disks you don't want a share to use, then use Excludes. This means that if you add a disk to the array, your shares will be allowed to use it with no action on your part. [if you don't want them to use the new disk, you'll have to add it to the excluded list.] Also, don't forget that in addition to the includes/excludes for each share, there is a global setting for these as well. In general, I think its best to leave both blank on the global settings -- I've seen several cases where folks had globally "included" all their disks, but months/years later they added a disk to the array, and didn't understand why it wasn't being used.
Archived
This topic is now archived and is closed to further replies.