duro

+1 I use file extensions in my file placement rules, but doing it by file size would make things simpler (no need to remember to add new extensions not already listed).

Hello again! Just wanted to come by and say I looked at the procedure I would need to go thru to accomplish this with multiple pools, and well, are you familiar with Ptolemy's geocentric map of the solar system? (over-complicated and wrong) I'm not above begging if I need to, but for now I'll just say please consider this simple addition to a great application.

Not many. I don't currently use any plugins, but when I did, it was only the SSD plugin, and it pretty much worked, until it didn't, and then I guess I just stopped using it after a while. Maybe you are skipping to the end of the SSD plugin journey? I notice the OP has "File placement rules respect real time blah blah blah" unchecked. I'm pretty sure I always had that checked when it was working. But that may have nothing to do with it.

Ditto. But I'm optimistic since they've obviously been doing a ton of development. The new 2.3.2 install file is at least three times the size of 2.3.1. I don't know what that means but it sounds like a lot of work. Maybe they didn't respond to your ticket because they thought it was fixed in the new release? I'm just trying to be positive..

I would disable all the other balancers and see if it that fixes it. If so then you can add them back one by one, carefully considering whether you need them and the potential complications they bring, such as this issue, if in fact the issue is one of those other balancers.

You're alive! Thanks, but that solution seems decidedly less simple than a checkbox next to each disk listed in the plugin. Your solution is complicated enough that as a DP user for many years, off the top of my head I have no idea how I would do it. Pool within a pool? Do I use multiple pools and combine them into one, or do I end up with separate pools? I just don't see anything simpler than a single pool and a checkbox next to each disk in the plugin.

Oh. I see Drashna hasn't posted since July. Shit.

I think it would be great to be able to select which disks the equalizer will equalize. Happy to come up with use cases if necessary, but I think it's pretty obvious why this would be useful.

Christopher, I do thank you for responding and offering to help, but instead of drilling down to discover the root cause, I've decided to go ahead and just rearrange things to avoid the problem in the future. I'm going to purchase another 10TB drive to replace the 4TB. I'll put the two 12TB drives in one enclosure, and the two 10TBs in the other. That way Scanner won't have the opportunity to get the sizes mixed up. I'll probably end up restoring 20 or 30 TBs of data from backup, but hey that's what backups are for. Thanks again. And for the record I'm still happy with the Stablebit software. I knew when I got these enclosures they were going to screw things up somehow. They're just too convenient. Of course if my plan backfires, I'll be back to open that ticket.

No I have definitely not opened a ticket. The misreported drive is a WD100EFAX. It shares the enclosure with a WD121KRYZ. The enclosure - which is technically more of a docking station - is a Wavlink ST334U. I've been on the latest stable release of Scanner - 2.5.6.3336 since shortly after it was posted, I believe. The issue first appeared with the last stable release. I have never installed a beta or release candidate version of Scanner.

Hi, I love Scanner and DrivePool and I have nothing but good things to say about them to anyone who asks, but this problem is a bad one and I need help. A couple months ago after running perfectly for at least six months on a new build, Scanner started reporting the size of one disk out of my four disk pool incorrectly (reported 10.9TiB when actually 9.1TiB). Both DP and Windows 10 x64 reported the correct size. I might have left it this way, since it didn't seem to cause any actual problems, but then Scanner tried to run a regular surface scan on that disk and immediately found unreadable blocks. I surmised it was trying to read blocks that didn't exist. To fix the situation, I went to Scanner's advanced settings and clicked the "Reset settings..." button. This worked! All drive sizes were then correct, and all drives passed their surface scans. DP and Windows still showed the correct information. BUT then I restarted the machine. When it came up, 2 of the 4 drives, one of which was the original misreported disk, had lost their partitions completely. After a lengthy restore from backup, finally everything seemed in order - all drives were the correct size, no errors during scanning. And that's the way things stayed through many restarts for at least the last several weeks, but now after the most recent restart the original issue has popped up again. The same 10TB disk is again being reported as a 12TB disk in Scanner while DP and Windows report it correctly. I haven't tried to scan it - in fact I've disabled automatic scanning for that drive. I'm sure this has something to do with the fact that I'm using two USB enclosures for these drives - 2 drives per enclosure. One enclosure has a 12TB and a 4TB, the other has a 12TB and the misreported 10TB. (I imagine this would never have been an issue if I were using a pair of identically sized drives for each enclosure.) It's just so strange that Scanner would be the only place the problem shows up. I'm currently running 2.5.6.3336, but the issue first arose with the last stable release, whatever that version number was. Please if there is any way to correct this problem without ending up in another 48 hour rebuild, I would appreciate any advice. For now I just have to live without scanning that particular drive.