rbutler81

Thanks for all the info. One last question, I have read striping turned on / been on for years.. what's so buggy with it? Would I notice a difference with it turned off?

Hey all.. long time user. My pool is 50TB in size, with two, 1TB SSD 'buffer' drives - I have a few questions: 1. It's my suspicion that turning off 'Real-Time Duplication' will give me a performance boost, is this true? I use duplication, but it seems like doing it at night is a good trade-off for added performance. 2. Would my pool benefit from two more 1TB SSDs? If I had four, and all the writes hit these drives before being copied at night to my archive drives, would I achieve faster write times to the pool? If so, any ideas on how much I'd see? 3. If I had four SSDs with real-time duplication turned off, and there's 5 or 6 concurrent writes to my pool, does DrivePool try to equally share those writes across the four SSDs? My balancing rules, in order, are: 1. SSD Optimizer (with no 'ordered placement' rules enabled - just SSDs vs Archive disks checked, and drive fill limits of 90%) 2. Duplication Space Optimizer 3. Disk Space Equalizer (equalize by percent used: 95%) That's it - could I benefit from more or less balancer plugins? Thanks a lot!

I did the same thing as you... I deleted my drive, and started a new one. I uploaded about 7TB to that drive. It's been working fine for about a month, but in the last few days as started giving Checksum errors again, and not uploading. What is going on? How have I been able to use Clouddrive for years and not have this issue, and now twice in a month? Is there anything else to try?

Hi there, I've already done some scanning of the forums, but haven't found anything conclusive... ... I have a Google Drive mounted CloudDrive, I'm using ver 1.2.1.1539. It's been working fine for a long time, but recently, I think maybe after an unexpected power outage, I'm receiving this error: I have 21.2 GB in my upload queue, that will not upload, but there's data constantly being downloaded (as witnessed in the UI). Is there something I can do to fix this? I can submit troubleshooting data against this ticket if that helps. Thanks in advance, R

Hey guys, thanks for all the suggestions. It actually sorted itself out somehow.. I didn't make any other changes, and when I checked it the next day the gray "other" space was gone.

I tried a few things.. but I still have this gray area showing. Any ideas? There isn't a way to see a list of files that falls into "other"? Also, check the screenshot below, I'm not getting the light blue arrows anymore, except for on one drive. I'm not sure if that matters, but it used to be there.

Hey thanks for the reply.. I checked those things just now. Doesn't appear to have the GB of data that is showing as other.

Hi there... I have a portion at the end of each of my drives in the pool that's gray, and described as "Other" data. I checked the drives, there isn't any data outside of the DrivePool folders - so everything should be part of the DrivePool. It's my understanding that if I added data to a drive outside of the DrivePool folder it would be recognized as Other. I've tried remeasuring, reduplicating, rebalancing.. all of which have left the drives with "other" data. Any ideas on how I can figure out what this is? Thanks.

Hi all... there doesn't appear to be a way to do this, but maybe I missed it. I'd like to be able to schedule upload throttling on my cloud drive. Example: middle of the night when no one's using the internet, remove throttling (or set it to very high value). In the day when the internet is being used, throttle to 50% of upload bandwidtch (for example). If Cloud Drive is saturating my upload bandwidth, the quality of my internet for other devices drastically drops. I've played around with finding that 'sweet spot', but would love to schedule throttling. Thanks.

I'm guessing this hasn't been rolled into the public release yet? I'm experiencing the same thing today on the newest public... I just downloaded the latest beta and installed it. Is there anything I have to do for this 'reorganization' to work, or does it happen without me explicitly telling it to? Thanks.

I'm getting a "The file or directory is Corrupted and Unreadable" error when I'm trying to access a folder in my cloud drive. I can't even delete it, which would be fine if I could. I ran chkdsk /f /x - found a bunch of problems, but this one still remains. the cloud provider is Google Drive, although I don't think that matters. Any method of forcing a deletion of a file (Windows 10) involves deleting the file during Windows boot, which can't happen in this case because the cloud drive isn't mounted at that point. Any ideas on what I can do here?

Hi there, I have a CloudDrive hosted on my Google Drive account. I've never had too many issues with it, other than occasional disconnects. Lately however, whenever I reboot my server, I've been getting notifications from Stablebit Scanner that this particular drive is damaged. When I open Scanner to have a look, beside the CloudDrive it says "File System Damaged." I've run chkdsk on it from a command prompt, it doesn't find any errors. I've also used Stablebit Scanner to try to fix the drive, but this also says there's nothing to fix when it runs. As far as I can tell, the drive is working. So, I'm not sure what this 'file system damage' is affecting. Can anyone help me with this? How to get it resolved? How to know what the damage actually is? I can attach any info that may be needed. Thanks.

Hmmm... ok. I know about your Contact Us page but I thought I'd post it here in case anyone else someday had the same issue. I'll contact via the link and post what I find.

- bump - anyone?

DrivePool is telling me I have 753GB of files that cannot be moved because it can't satisfy the file placement rules. For the life of me I can't find what the conflict is, I didn't change anything... I added a new drive and set up some rules for it - those rules worked because I have the data I wanted on that new drive. Is there a way to see exactly what the conflict is? A way to see which files this message is referring to? Or which rules this is referring to? It would make it a lot easier to get this sorted out... In a log file somewhere? Thanks.