October 25, 20241 yr 1. Can some of you please share your thoughts on how you use this? Is it a good idea to heavily rely on this and create my shares so that all use disjoint subsets of my disks for clearer data layout as opposed to "any can be anywhere"? 2. Why is it not a good idea to mix local and global include/excludes? 3. It would be nice if the docs elaborated on this feature further and how it affects the rebuilding processes in case of disk replacement. For example I imagine a parity disk won't help too much if a share is set to include only 1 disk (or 2 disks in case of 2 parity disks), are such low numbers even allowed?
October 25, 20241 yr Community Expert Solution 1. Really up to you. Not sure that there is any specific reason above how you want to control your data replacement. 2. Only reason is that often users forget they have set something at the global level and wonder why a disk they then add does not get used. 3. Not relevant to rebuilds as parity has no data, and the rebuild works at the disk sector level and has no idea of the meaning of the contents of any sector.
October 25, 20241 yr Author Alright, I get it. Thanks! But the reason is that as I described it's more straightforward to access the data without unRAID in my opinion. Edited October 25, 20241 yr by steelsoap
October 25, 20241 yr Community Expert 53 minutes ago, steelsoap said: But the reason is that as I described it's more straightforward to access the data without unRAID in my opinion. Do you mean without using Unraid OS at all or something else to handle network storage?
October 25, 20241 yr Author Yes without Unraid OS, just mounting the subsets as JBODs read-only for whatever reason. Edited October 25, 20241 yr by steelsoap
October 25, 20241 yr Community Expert 45 minutes ago, steelsoap said: Yes without Unraid OS, just mounting the subsets as JBODs read-only for whatever reason. Using what OS?
October 25, 20241 yr Community Expert I do use the Share Exclude on the array of my main server. I have my media library share exclusively on two of the disks in the array. All of the rest of the shares reside exclusively on the other three disks in the array. The main reason for this is that my Plex clients sometimes time out with an error if it takes too long to spin up a disk. So I keep the two disks containing media always spun up, and the other three disks can spin down after a short time of inactivity.
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.