scottmlew

Anyone have any insight to offer?

See the example below -- why are some of my drives appearing multiple times? I also noticed terrible UI performance...like the drive list takes 10 minutes (seriously) to populate after clicking a folder. And now I've made my change and hit save, and the UI is not responding and has been like that for maybe 15 minutes or so. And I guess the performance issues aren't just with the UI...after a reboot, it's been over two hours and the service still hasn't started.

Still looking for an update on this...

Any update? I licensed several products assuming this issue would be fixed, but DP is still not particularly useful to me given this issue.

Thanks for bumping. I'm using 2.1.1.561 running on 2012 R2.

I was wondering if there is any update on this?

I have verified again right now, and those settings are as you indicated (screenshot attached)

Chris, thx for opening the case. That makes sense re: the .covefs folder, and it is on the first 3 drives I added to the pool, so all is well there. I tried disabling all balancers except Ordered File Placement (OFP) and saw the same unexpected behavior (files going to d04). Then i disabled OFP as well, and got the expected behavior (files going to d05). I reenabled the other 2 balancers (StableBit Scanner and Prevent Drive Overfill) and am still seeing the expected behavior. So, OFP seems to be the culprit (or at least contributing to the issue).

I have a log file now and will send to you directly. Exact situation as described in the original post. I copied in to the file share for Folder_B ("TV" when you look at the log files) and the files end up on d04. I've tried this locally on the server itself (no share involved) and seen the exact same behavior. I also tried with the option to balance immediately (and I even unchecked the "no more often than X hours" box) and still see the same behavior. I did notice that only 3 of my drives have a .covefs folder. Not sure why that is, or if it is important. The drives WITH the .covefs folder are d01, d02, and d03...so neither the drive that should get the files, nor the drive actually getting the files, has the folder.

Does this mean that the file placement rules are not immediate? i.e., files may be put on a disk that the rule prohibits them from being on and then later moved to an approved disk?

Hi Chris, I will gather some logs when I am next able to access this box (likely not until the weekend). In the meantime, though, I guess I should verify 2 things: 1. since I am using SnapRAID I have "do not balance automatically" selected, to avoid extraneous file movement. I wanted to confirm that this is correct. 2. with the file placement rules, the files should be put on the "correct" disk as soon as they are copied to the pool and a rebalance shouldn't be required to get them in the correct place....right?

Hi Chris, thx so much for the quick reply. Unfortunately, even after those changes to the config, I am seeing similar behavior...now all files are being put on d04. I even tried restarting the DrivePool service, but the same thing is happening.

I have 3 balancers active, plus file placement rules, and I am not seeing the file placement behavior that I expect. The 3 placement rules are: Stablebit Scanner, Prevent Drive Overfill, Ordered File Placement. For file placement rules, i have a couple of entries for recycle bins that I'm ignoring, plus Folder_A which is marked for drives d01-d04 and Folder_B which is marked for drive d05. When I copy directories into Folder_B on the pool, the contents are split between d04 and d05 in a round-robin manner. This does not seem like the expected behavior since the copied files should match the rule for Folder_B and go only to d05 (which is essentially empty, so nowhere near the limits of the Overfill or Placement balancers). Any ideas why it is doing this?