Christopher (Drashna)
-
Posts
11568 -
Joined
-
Last visited
-
Days Won
366
Posts posted by Christopher (Drashna)
-
-
-
Also, make sure that you're up to date. There was a recent release, and there was some updating to the Cloud integration code, that may affect this.
-
I'll post it here too.
There is a fix in the latest betas involving memory corruptions of file IDs.
However, ... the issue may also be the wrong API being used:
Quote... incorrectly using File IDs as persistent file identifiers, which they should not be. File IDs in Windows can change from time to time on some filesystems.
Source: https://learn.microsoft.com/en-us/windows/win32/api/fileapi/ns-fileapi-by_handle_file_information
The identifier that is stored in the nFileIndexHigh and nFileIndexLow members is called the file ID. Support for file IDs is file system-specific. File IDs are not guaranteed to be unique over time, because file systems are free to reuse them. In some cases, the file ID for a file can change over time.
If this is the case, then it is expected behavior.
The correct API to use to get a persistent file identifier is FSCTL_CREATE_OR_GET_OBJECT_ID or FSCTL_GET_OBJECT_ID: https://learn.microsoft.com/en-us/windows/win32/api/winioctl/ni-winioctl-fsctl_create_or_get_object_id
Object IDs are persistent and do not change over time.
We support both Object IDs and File IDs.
-
If you want to use the SSD Optimizer and use the rest of the pool, the "simplest" option may be to use hierarchical pools. Eg, add the SSD/NVMe drives to a pool, add the hard drives to another pool, and then add both of these pools to a pool. Enable the SSD optimizer on the "pool of pools", and then enable the balancers you want on the sub-pools.
-
Unfortunately, some enclosures do this. Fortunately, it's not very common, but it sucks when you find one that does.
-
I believe that you've opened a ticket for this already, and I've replied there.
-
Make sure that you're changing the "override" value, and not the default.
The default may get overwritten, but the override value shouldn't.
-
Well, the biggest issue is that the folders are likely not actually empty. There are some hidden files that are in use by StableBit DrivePool. For instance, we use Alternate Data Streams to set the duplication settings. These don't show up normally, even with enabling the "show protected system files" option.
-
Sync.com cannot be added, as there is no publicly documented API. Without that API, and a way to officially read and write files/data on the provider, there is no way to support it.
-
No, no changes have been made, in this regards.
-
That's positiviely bizarre. Though, I can't really say that it's surprising, unfortunately.
-
YOu can use the "Quick settings" to reset these values.
And the different profiles do have slightly different profiles.
As for the settings, and what they do, there is some basic information about that here:
https://stablebit.com/Support/Scanner/2.X/Manual?Section=Scanner -
Setting the balancing ratio to 100% may help.
But to be blunt, the SSD Optimizer and the Disk Space Equalizer balancer are at odds. The Disk Space Equalizer wants to fill every drive, equally, but the SSD Optimizer wants to clear out several of the drives.
-
There isn't a set amount of time, because tasks like balancing, duplication, etc run as a background priority. This means that normal usage will trump these tasks.
Additionally, it has the normal file move/copy issue, estimates can jump radically. A bunch of small files take a lot more time than a few large files, because it's updating the file system much more frequently. And for hard drives, this means that the read/write heads are jumping back and forth, frequently.But 6-12 hours per TB is a decent estimate for removal.
-
could you open a ticket at https://stablebit.com/contact about it?
-
Glad to hear it!
-
That's definitely not normal, but I think you've already opened a ticket for this, as well.
-
StableBit Scanner won't repair the drives. Eg, it never writes to the drive (the exceptions being the settings store, and if you run file recovery)
That said, it will rescan the drives, and update the results.
The important bit here is the long format, though. This writes to the ENTIRE drive, and can/will cause the drive to reallocate or correct bad sections of the disk. As for not correcting right away, it has to run the scan again, and unless you manually cleared the status, it won't do this right away, but will wait for the 30 days (or whatever it is configured to)
-
5 hours ago, Gabe said:
Just to clarify based on the second half of your post... Am I correct in interpreting that if I set up any drive (cloud, local, NAS share, etc) in CloudDrive, and I add that to a pool of only CloudDrives in DrivePool (X:), hardlinking could theoretically work on X:? And if that's the case, would there be issues in terms of balancing?
Thanks!
No. Hardlinking doesn't work on the pool drive, at all, and never will. The hard links are an object/feature of the volume, not the disk, and require that all instances of the file be on the same *physical* volume.
They work on StableBit CloudDrive, because it doesn't emulate the filesystem the way that StableBit DrivePool does. It handles things on a block level (below the file system, basically), and never directly deals with the file system. Because of this, just about anything you can do on a normal disk, you can do on the StableBit CloudDrive disks.
But if they're pooled, then the pool's limitations still apply (at least to the pool drive).
-
Could you open a ticket at https://stablebit.com/contact for this issue?
-
Correct. Duplication is inheritted unless explicity set. Enabling pool file duplication enables it for the root, and everything else gets inherrited. And when you change it, it checks to see which files need to be duplicated or unduplicated (the "checking duplication" part that you may have seen). So, it shouldn't mess with the existing data.
-
On 8/31/2023 at 1:11 PM, beatle said:
Maybe it works now, but my trial expired last week. What a shame.
As shane said, please contact us.
Also, even with the trial expired, the software will continue to work, but the upload is incredibly throttled , so you can get data off but makes it impracticle to use.
-
11 hours ago, tphank said:
With the beta, should the clouddrive be set as read only?
Yes. This has the effect of telling the virtual drive that it is read only, and that files cannot be written to it. Otherwise, it may start filling up the cache with new data.
-
In general, the Microsoft store apps have some additional/unusual storage requirements, and may not work on the pool. This includes the xbox applications.
Google drive not supported after may 2024? Why?
in Providers
Posted
Alex has said that he plans on postind on the forums an announcement about this, and it may be best to wait for that.
That said, between the fact that Google Drive has always had a 750GB per account per day upload limit (which is pretty low), some of the odd issues that pop up with it, and that they've recently limited to 1TB (or 5TB) of data and lock the account if it exceeds it (eg, stops uploads), the writing has been on the wall for a while.