Christopher (Drashna)
-
Posts
11328 -
Joined
-
Last visited
-
Days Won
338
Posts posted by Christopher (Drashna)
-
-
Awesome, I'm glad to hear it!
-
Shadow Copies is the name for the code/feature that supports Previous Versions, and other features of Windows (such as must backup solutions).
It's not part of StableBit DrivePool.
That said, if you wouldn't mind, I'd like to take a look at your system directly, and poke around. I may be able to identify and fix the issue a lot faster that way.
If you're okay with that, head to https://stablebit.com/Contact and open a ticket. -
The simple option, is you don't. Disable shadow copies, and delete them.
The System Volume Information will continue to come back (it's a hard coded Windows behavior), but that will reduce the usage.
If you run "control system", it's the "System Protection" option. Turn it off and delete them for each disk, in question. -
It means that you may have issues accessing data on the pool through WSL.
Namely, WSLuses a layer between WSL file system and windows for the file system that can cause issues for DrivePool (eg, potentially unsupported commands, etc). And adding support for it is not simple.
-
Specifically, the "SSD Optimizer" uses the "drive is being emptied" option, so can if that option is checked (default), it means that the balancers (SSD Optimizer) won't follow file placement rules for the SSD drives, and will empty them, regardless of the rules.
Unchecking the "unless the drive is being emptied" means that it will always respect the file placement rules.
In both cases, it will still work as a write cache.
-
As mentioned, there is nothing wrong. It's just that the placement means that duplication can't be used for a large portion of the pool.
If you have no plans on using duplication, then you can safely ignore this, and may even want to disable the mentiond "Duplication Space Optimizer" balancer.
-
Try resetting the permissions on the pool:
https://wiki.covecube.com/StableBit_DrivePool_Q5510455 -
Sorry, no, WSL is still not supported.
-
https://dl.covecube.com/DrivePoolBalancingPlugins/SsdOptimizer/Notes.txt
Quote* If you've created file placement rules that are attempting to keep files on drives that are designated as SSDs,
then you should disable the "Unless a drive is being emptied" option, under the "File placement settings" category,
on the "General" tab. Otherwise, your File Placement rules will not be respected by this plugin (because it is
emptying the SSD drives). -
-
Based on the other posts, I'm guessing that file system corruption has occurred on one of your drives ("U:\"), and you need to check for "found.###" folders (run a chkdsk pass, and then check), or run data recovery.
-
Unfortunately, this is very unlikely to be added, as we have no intention of spreading the contents of files between multiple drives.
However, you could use Storage Spaces or RAID, and add that drive to the pool. And you can use the balancers and/or file placement rules to get this sort of behavior.
-
Is there anythong outside of the PoolPart.xxxx folder on the drive? including shadow copies, lost files restored by checkdisk, etc?
Using something like windirstat or wiztree are a good way to find and visualize the data on the drive.
-
What the error message has said: the data returned does not match what is expected. It has been corrupted or altered, or is using older data from a failover.
https://stablebit.com/Support/CloudDrive/Manual?Section=Recovering from Errors
-
Have you tried the commands and settings from my previous post, and from op's post?
-
There isn't a whole system option, currently.
Adding support for it may be possible, but may not be simple to implement.
That said, you can set the defaults in the main UI.
Request added: https://stablebit.com/Admin/IssueAnalysis/28678
-
I'm glad that you were able to find a solution that works for you.
However, consider it requested: https://stablebit.com/Admin/IssueAnalysis/28677
-
Could you open a ticket for this, at https://stablebit.com/Contact?
-
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?
Need pool to be taken offline when a drive drops out OR way to query pool status from a remote machine
in General
Posted
Would something like a file on the pool noting that it's read only work here?