November 11, 20169 yr My /Books share is set to include ALL disks (see attachment #1). At the moment, I'm migrating from reiserfs to xfs, so I've excluded the 2 disks currently involved from user shares so nothing new gets written to either of them during the process (see attachment #2). When I look at the /Books share to see where the data actually resides, it's spread across 3 physical disks, but WebGUI reports that ALL of them are outside the list of designated disks! (attachment #3). Why does it think that Disk11 is outside the list of designated disks? It was a couple of days ago when I was moving data off of disk11 to reformat it, but it's no longer excluded. Additionally, I'm not entirely sure why it thinks there is 5.6 GB of files there, I've only got 805 books organized into my library at the moment, and even though some have PDF and MOBI or EDOC, it shouldn't be that huge...
November 11, 20169 yr Have you restarted the array since you made the changes in exclusions? The whole User Share system is created fresh when the array is started, so whenever you see something in the shares that doesn't look right, just stop and restart the array. Also click the Help button, and check the syntax for the exclusion box. It almost sounds like it's considering your syntax as a range from Disk 7 to Disk 12, not a list.
November 11, 20169 yr I don't think there's anything wrong. I'm fairly sure that "All" in the context of a share means all of the disks that are allowed to be used for shares. The Global setting determines what that actually encompasses.
November 11, 20169 yr Author Yes, I had to have restarted it - you have to stop the array to make changes to the global share settings. I unchecked the Disk11 box and checked the Disk7 box to get the global level exclusions, then restarted the array once it had saved the changes. I did not do an additional stop/start after that, however. The help text from the 'Excluded Disks' setting: This setting defines the set of array disk which are excluded from User Shares. Uncheck all disks in order to not exclude any disks When I'm done verifying the copied files, I'll try stopping and restarting the array to see if it clears Disk11. Thanks for the feedback!
November 11, 20169 yr Author I don't think there's anything wrong. I'm fairly sure that "All" in the context of a share means all of the disks that are allowed to be used for shares. The Global setting determines what that actually encompasses. Am I totally misunderstanding? I would have thought that the Global setting overrides the individual share setting, so for the share include all, exclude none is overridden by the global Exclude 7 & 12. However, the question is why is the Books share claiming that Disk11, which isn't excluded anywhere, outside the "list of designated disks"? Unless, of course, it's outside the list of excluded disks, but that's being a bit sarcastic...
November 11, 20169 yr The Global setting DOES override the individual share settings. As I said above, setting an individual share to "All" does NOT mean all of your disks -- it means all of the disks that are available for shares (i.e. those that are included in the Global share settings). As for the "outside of designated disks" list => It makes sense for #7 and #12 ... it's just noting that there is data on those disks for the share even though they are not included in the share settings (because of the global exclusion). I do NOT know why disk #11 is showing there. Unless it WAS in that state, and for some reason the display hasn't been updated.
November 11, 20169 yr Author I did have disk11 globally excluded a few days ago, but, as the screen shots show, it is no longer globally excluded. It's not excluded from the Books share, and yet, the share settings seems to think that it's excluded. I can browse to it from Win10 with no issues. I can read from & write to it with no problem, it's just that it looks like it's excluded, and that makes zero sense.
November 12, 20169 yr I did have disk11 globally excluded a few days ago, but, as the screen shots show, it is no longer globally excluded. It's not excluded from the Books share, and yet, the share settings seems to think that it's excluded. I can browse to it from Win10 with no issues. I can read from & write to it with no problem, it's just that it looks like it's excluded, and that makes zero sense. Do you mean browse to the Books share or browse to Disk 11? One is a User Share and one is a disk share, and their settings are independent, separate. Exclusions do not apply to disk shares.
November 12, 20169 yr Author The whole point is a bit moot by now, since I've reformatted disk7 as xfs and files are being copied back to it. Do you mean browse to the Books share or browse to Disk 11? One is a User Share and one is a disk share, and their settings are independent, separate. Exclusions do not apply to disk shares. I could see the files from the "Books" share. What was odd to me was that when I clicked the "compute" button on the WebGUI page, it reported that /mnt/user/Books was spread across 3 disks (7, 11, 12), and that it listed all of those disks as being "outside the list of designated disks". I fully understand that the logical share "Books" had a physical presence on the three different physical disks, what I don't understand was why it thought that the physical disk11 was outside the set of "designated disks", since there was no share-level or global-level exclusion preventing virtual "Books" from existing on physical "Disk11". Again, this point is now moot because I've finished my move/format/move cycle for physical Disk7, but for academic reasons, I would like to understand why it thought Disk11 was outside the designated disks. However, since I've changed the "Books" share definition (it now includes Disk7 only), and I will be moving all files from disks 11 & 12 to disk7 to ensure it's all contained in one location (no, don't ask why, for some reason that just makes sense to me), I won't be able to reproduce the situation, so it will, most likely, be very difficult to debug/trace/understand from here.
Archived
This topic is now archived and is closed to further replies.