Christopher (Drashna)

Not directly. The best way to do this is to add the pool to a pool, itself. Then add the iSCSI volume to this top level pool, and enable duplecation there. this would ensure that a copy of the file exists on the local pool, and on the iSCSI volume. You'd need to seed the pool, and change the duplication settings, but aside from that, should be very doable.

Do you have duplication enabled on the pool, by chance?

You can definitely do (most) of this. You can't specify which data to keep locally, but it should be intelligent about what to keep. Eg, the most often you use stuff, the more it will keep that data in the cache. And if you're using a 1TB drive, and set the cache to use most or all of that drive as the cache, it will fill up that drive, and keep all of that content in the cache. However, keep in mind that on the NAS, you'd see the disk data chunks and not the game files.

Yeah, you want to run it on both systems, and you want to reboot after running it to ensure that it takes effect.

Have you messed with the autotuning? if not, that is the usual culprit. Setting it to highlyrestricted can help, a lot. Try running this on any system involved: netsh interface tcp set global autotuninglevel=highlyrestricted And reboot the system.

There is an option in the Folder Protection window to show hidden folders. is that what you're looking for?

Could you open a ticket at https://stablebit.com/contact/ then?

Generally, this means that the chunk has disappeared from the provider, which is definitely "not good". However, if this is google drive, then the issue may clear itself up, after some time.

Which software are you using? And in theory, it shouldn't.

Either the data is corrupted, or ... most likely, there may be an issue with the cache drive. unmount the drive, and run a CHKDSK on the cache drive (or schedule one for the next boot).

Shouldn't be. I actively game off of a pool, with no issues.

Make sure you have the latest version of StableBit DrivePool. If you do, then it's included already. You just need to activate it.

Unfortunately, no, there isn't a way to do this, that wouldn't potentially cause serious issues.

https://stablebit.com/DrivePool/Download Once you click the checkbox, there is a "what's new?" link that will take you to here: https://stablebit.com/DrivePool/ChangeLog?Platform=win Or you can see the beta changelog here: https://dl.covecube.com/DrivePoolWindows/beta/download/changes.txt

If you're using the latest release, you shouldn't need to install it, it should be pre-installed. Otherwise, you need to install it, and then open the balancing settings in StableBit DrivePool. You'd see them here: https://stablebit.com/Support/DrivePool/2.X/Manual?Section=Balancing Plug-ins

I'm not exactly sure what you mean. Also, there are some command line utilites that deal with getting information about the pool, but would need some processing to be able to be displayed in a meaningful way. For instance: [HOWTO] File Location Catalog - General - Covecube Inc. check-pool-fileparts - Nuts & Bolts - Covecube Inc.

Have you seeded the top level pool? If not, then you may need to do that. https://wiki.covecube.com/StableBit_DrivePool_Q4142489 Also, don't use A:\ for the drive letter. Windows has some hard coded behavior that expects A:\ and B:\ to be floppy drives. This includes querying those drive letters frequently, which will keep the pool (and all the drives in it) awake.

This depends on a number of factors, but over time, it should do this, actually. Specifically, by default, StableBit Scanner should only be scanning one disk per controller. If you have multiple controllers, then that will increase the number of drives that scan at one time. Also, make sure that you have enable the throttling options that you want. You can see these here: https://stablebit.com/Support/Scanner/2.X/Manual?Section=Throttling Also, the heat tab in the settings have some additional settings that may help: https://stablebit.com/Support/Scanner/2.X/Manual?Section=Heat But if you set a work window, that will reduce the amount of time that the drives can be scanned, and will help spread out when the drives get scanned, over the course of the month. And this is because, the 30 days isn't from the last time it was scanned, it was from the last time a specific region of each drive was scanned.

Have you tried manually running a CHKDSK pass on the disk in question? If not, try doing so and remeasure the pool. Also, the files are located in a hidden "PoolPart" folder on each drive, which should be accessible. See if you can reproduce the access issue on the drive in question. If you can, then it may be an issue with the drive that StableBit Scanner hasn't had a chance to pick up yet (the default is for 30 days, in most cases, so something may have happened within that window)". And if neither are successful, then open a ticket at https://stablebit.com/contact/

were you backing up the cache?

correct. Some of the drive "geometry" can't be changed after it's been created. You would have to destroy the drive and recreate it to change those settings. Also, some of it can be changed, but the process is dangerous or requires reformatting. So it may be simpler to just recreate, since you could have both running at the same time.

That's very unusual, and I haven't seen anyone else report it. If you could, open a ticket at https://stablebit.com/contact

that's rather odd. Could you open a ticket about this at https://stablebit.com/contact?

To clarify, StableBit DrivePool doesn't use the drive letters or mount points. It uses the volume ID for the disks. So you can change how the drive is mounted without any issues. Personally, I prefer mounting the drives to folder paths, as that hides them, but still allows them to be accessible.

There are some hidden by default, already, but that's because they're experimental. But I don't see a reason why this couldn't be added. StableBit Scanner uses Telerik controls, which we stopped supporting/using, since they come with a bunch of their own issues. StableBit DrivePool and StableBit CloudDrive use entirely custom implementations, and all native WPF controls, because of some of the issues we've had with telerik controls. So, pretty much the opposite. Eg, StableBit Scanner is the older product (the first, actually).