Leaderboard

doing checkdisk fixed my corrupted file, i'm doing remeasure again as drivepool didnt finish remeasure because of the corrupted file. Any ideas what may be causing drivepool to prefer to write on older hdd?

Solved: Moving and defragging the MFT and related $ files to a location 5% into the platter, and a reboot.I extended the MFT to a 1 GB(700mb free) in size just to be on the safe side. Yay sustained 200mb+/sec is back.

I found when copying to the pool it defragments files quite badly. My solution to it is ultimatedefrag. Although any folder/file layout defragger will do just fine. I'm old school and obsessive about track to track seeks, power usage and head flying hours. One of the things i've read often mentioned here is how old your drive is. Really the question should be is the drive under 40,000 flying hours thats my benchmark for an old drive where failure rates increase to a significant level. One of the useful things i use is in the power settings, the ability to ignore burst traffic fo

Are you going to head back to StableBit DrivePool and make some updates and add some of the posted suggestions? This is fantastic software and I hate to see it stagnating.

Just a heads up, yes, it does continue to attempt to upload, but we use an exponential backoff when the software gets throttling requests like this. However, a daily limit or schedular is something that has been requested and is on our "to do"/feature request list. I just don't have an ETA for when it would be considered or implemented.

Hello, I've noticed recently that Drivepool deals with "Size" vs "Size on disk" differently inside and outside of the pool which causes drivepool to think the drive is bigger than it is. From what I can tell: When files are outside of the pool it uses the "Size on disk" i.e. "Used space" reported by Windows + "Free space" and calculates the size of the drive. When files are in the pool it uses the "Size" not "size on disk" to calculate used space + "Free space" to calculate size of the drive. This causes a discrepancy in the size it believes the drive to be and ca

Deduplication, ntfs compression, and "slack space" can all account/contribute to this.

As you mentioned, the simplest method is to physically disconnect the drive or take it offline via Windows Disk Management; both will result in DrivePool noticing the disk is missing, allowing you to Remove it without affecting the files - however if you don't rename or remove the poolpart folder (a "hidden" folder on the drive) before reconnecting/onlining the drive again it may be rejoined to the pool. To pre-empt that issue, you can either rename the poolpart folder before disconnecting/offlining the drive (though this may not be possible if there are any open file handles*) or you can

As I was writing the various providers for StableBit CloudDrive I got a sense for how well each one performs / scales and the various quirks of some cloud services. I'm going to use this thread to describe my observations. As Stablebit CloudDrive grows, I'm sure that my understanding of the various providers will improve as well. Also remember, this is from a developer's point of view. Google Cloud Storage http://cloud.google.com/storage Pros: Reasonably fast. Simple API. Reliable. Scales very well. Cons: Not the fastest provider. Especially slow when deleting existing chunks

LOL. I just recently did this on my own pool, actually. There isn't a good way. You need to format the drives to do this (or use a 3rd party tool, and hope it doesn't corrupt your disk). The simplest way is to use the balancing system. Use the "Disk Space Limiter" balancer to clear out one or more disks at a time. Once it's done that (it make take a few hours or longer), remove the disk from the pool and reformat it. Re-add it and repeat until you've cycled out ALL of the disks. Specifically, the reason that I mention the Disk Space Limiter balancer is that it runs in the

Well, Alex has covered the development side of this, I've been looking into the pricing of the different providers. While "unlimited" is clearly the best option for many here, I want focus on the "big" providers (Amazon S3, Azure Storage, and Google Cloud Storage). Unfortunately, for many users, the high cost associated with these providers may immediately put them out of range. But we still think it is a good idea to compare the pricing (at least for reference sake). All three of these providers include a storage pricing (how much data you're storing), "Request" pricing (how many API