August 11, 20178 yr Some fishy things are going on with my array as drives begin to near capacity. I have a share that has Included disks set just to Disk 1. A subset of the data (74GB) is now showing up on disk 11 (915GB). But like, it's the same data. As in, I can open the same PDF from disk 1 (accessing the exported mounted drive - not via a share) or disk 11. What would cause this? I always set up my shares to be confined to their assigned disk(s) as I don't like my data showing up in unexpected places... More curious, SOME of the data has the modified date of 8/15/2016 9:40am, which I noticed for other top level directories on disk 11. Whenever I access any directory with that modified date, I get a permissions error. I'm not sure why, let alone just for files on that date and exact time. Edited August 12, 20178 yr by TyantA
August 13, 20178 yr Author Ok, so either no one has seen this or I haven't explained myself well enough. For all my shares, I specify a disk using included disks. For some, I include multiple disks, for others, I just include one. In the case I'm talking about, I have only included one disk: disk 1. I assumed that including a disk is the same as excluding every other disk. I use high-water regardless of whether a share has one disk included or multiple. The (first) strange behaviour I'm seeing is what I would expect to see if disk 1 and disk 11 were included on the same share using high water. Some of the files just ended up on disk 11, as disk 1 gets full. Is that behaviour to be expected even if only one disk has been "included"?
Archived
This topic is now archived and is closed to further replies.