Christopher (Drashna)

Not really, unfortunately. It's all done through normal APIs, so "it's a windows thing/issue".

It follows the normal balancing, rules. But you can use the Drive Usage Limiter if you wnt to clear out a specific disk or two.

Try resetting the settings https://wiki.covecube.com/StableBit_DrivePool_Q2299585B If that doesn't help, open a ticket at https://stablebit.com/contact

No, it's not. Files are written to the "SSD", and then later balanced off.

If you are using symlinks, information about these are stored in the metadata folder, and that is set to x3 duplication by default.

You can set a work window for StableBit Scanner to run it's scans, yes. Also, over time, it should get better about when to scan the drives. And to clarify, it isn't an "all or nothing" for the scan. It keeps track of the areas on the disk that have been scanned, and when. So even if a scan gets interupted, it will pick up where it left off.

If VoidTools Everything is using the USN Journal to search for things, that would be why. It is not supported on the pool, and you need to fall back to a different method. Do you mean like a context menu in explorer that would jump to the underlying disks for the path in the pool?

Mostly, this. You can use utilities like WinDirStat to view the drives. But it's very possible/likely that you won't find anything specifically. Most likely, the difference is due to the size vs size on disk differences (slack space), as well as the System Volume Information folder on each disk.

Real-time placement limiters are different. They're mostly used by the Stable Scanner, Ordered File Placement and SSD Optimizer balancers to ensure that no files are placed on these drives. They're the "red arrows" you may see on the drives.

The SSD Optimizer balancer plugin causes new files to be written to the "SSD" drives (which you can pick), and then later balanced off of those drives. So sudden power loss or reboots should not impact the data, at all.

I just use column and row for my server chasis, but "bay #" for internal drives.

The main two reasons that this can happen. File system errors and chkdsk, which may lead to a "found.###" folder. the other reason is VSS snapshots, especially if the data on that drive changed a lot (such as balancing data off of it). That's normal. It's an artifact of how Windows manages drives. It has to have a size before we can properly calculate the size. So it's a placeholder. But if you notice, everywhere else, it reports the correct size. Nope. But I think it should still work for v2

Yeah, I believe that it should.

Thanks for letting us know. I can confirm this behavior, as well, and have flagged it. https://stablebit.com/Admin/IssueAnalysis/28645

There aren't any plans on doing so, ATM. That may change in the future.

Nice!

No, it's not, currently. And there are some issues with doing so, for a number of providers (eg, app folders, etc)

Internally, there has, yeah. But one of our goals for the pricing is to to keep it reasonable, so that it's attractive to everyone.

You will need to manually update the location information. In StableBit DrivePool, disable the bitlocker detection. That helps from that end. https://wiki.covecube.com/StableBit_DrivePool_2.x_Advanced_Settings For StableBit Scanner, throttle the SMART queries, as that usually helps. https://stablebit.com/Support/Scanner/2.X/Manual?Section=SMART As for the work window, that's defined in the "general" tab. So if you don't have a window set, then this setting doesn't do you much good. Meets or exceeds it. Also, there is a threshold setting to. It will warn you as it approaches that maximum. (default is for a 15C window) It's one disk per controller. So if you have multiple controllers, such as onboard, and a controller card, it can scan multiple disks. It checks the disks, and see if there are any disks with sections that haven't been scanned in "x" days, with x being the settings for how frequently to scan. There are some other factors, such as disk activity, etc. It means that the scanning is done in such a way that any normal activity takes priority over the scans, and may stop the scanning from occurring. This way, it minimizes the performance impact for the drives, ideally.

Awesome, thank!

You are very weclome! Correct. At least for that system. Reconnecting it should automatically re-activate, though.

lol. Well if it helps, IIRC, you can have multiple parity drives with SnapRAID, which I'd definitely recommend.

Yeah, the notification will remain until it's resolved. If you really, really must kill the notifcations, you an disable the notification.exe process. I don't recommend it, because you may (will) miss important notifications.

StableBit Cloud will sync the scan data, actually. So reconnecting it will get it back. You will want to delete the device in the cloud, IIRC. Correct, but that's not exactly how the scan works. StableBit Scanner keeps a sector map of the scanning progress. Different regions are tracked independently, and it's those regions that have to be older than "x days" (7 days in your example), when they're rescanned. Over time, this should cause the drives to be scanned when there is less activity, and should spread out the scanning over the week.

It can leave empty folders, especially if you're aggressively rebalancing the pool. That said, the folders may not actually be empty. Hidden files, for instance, may reside in the folders and not get balanced away. Also, there are alternate data streams that are used for duplication settings, so the folders may be empty, but they have settings tagged onto them.