![]() ![]() It only creates the chunks and uploads them to the cloud provider when data is actually written to them by the system. It creates the chunks to represent the entire drive all at once, so the amount of space you specify is also always the amount of space used on your storage device-in this case, a local drive.įor some providers, like Google Drive, CloudDrive does not create all of the chunks at drive creation. CloudDrive simply cannot tell you that.įor some providers, like the local disk provider, all of the chunks are created when the drive is created-so "Cloud Unused" isn't a relevant piece of data. To be clear: None of those show how much of the drive is actually used by data in the same way that the system sees it. Other tools exist for that, but no other tool exists to provide information about the provider usage. The charts provided in CloudDrive are for the purpose of monitoring the usage on the provider, not the drive. Simply looking at Windows Explorer, Disk Management, or Resource Monitor can provide you with volume usage information. You're talking about adding entirely new levels of infrastructure to the application to accomplish something that can be accomplished by looking at ANY other disk tool in Windows. ![]() It would have to look at ALL volumes on your drive and compare them to the maximum size, and even knowing what volumes are on what drives requires access to the file system which it, again, does not have. Which, again, it is not-because of how NTFS works. But at the level at which CloudDrive operates, that information simply is not available.įurthermore, the drive size can contain multiple volumes-so it can't really just look at some particular volume and compare it to the amount of data on the disk, even if the amount of data on the disk WERE representative of the amount of space available for new information. You can always, of course, simply open up Windows Explorer to see how much space is available on your drive. The file system, at the OS level, handles that information. ![]() You specify a size because that is the amount of space that CloudDrive creates in order to store things, but whether or not space is available for USE is simply not something that the drive infrastructure is aware of. ![]() Otherwise I have to do it manually by checking via FTP-Software how much data I have uploaded.Īgain, CloudDrive itself has no way to know that. This might be a feature request, but CloudDrive could check how much data is already on the CloudDrive and compare it to the specified drive size. So basically I have to upload data and at some point I will get the message that the drive is full. Generally I find it a bit confusing that you specify a drive size for the CloudDrive although you will never know how much space is taken. This is one of the distinctions between a tool like CloudDrive, which operates at a block-based level like a local disk drive, and a tool like Google File Stream or rClone, which operate at a file-based level, and are aware of the file system itself. So from the drive's perspective, that space is still used, even though the system doesn't actually look at it that way. As far as the drive is concerned, nothing has changed in that area of the drive, but NTFS still considers it available. So if you delete a file, NTFS simply marks that file as deleted and remembers that the space used by that file can now be used for new data. It operates at a file system level, and, as such, is aware of how much of the space on the disk is actually currently in use.Īnother way to consider it is this: NTFS does not generally modify data on delete. In order for CloudDrive, or your HDD's firmware, to be able to tell you how much space is available for a particular purpose, it would have to somehow communicate with the file system-and neither does that. It might be able to tell you if a particular portion of the drive has been written to at least once, but it can't tell you how much space is available on the drive because it simply doesn't operate at that level. Think of the CloudDrive software as analogous to the firmware that operates a hard drive. Christopher can correct me if I'm wrong, but my understanding is that CloudDrive, as an application, is simply not aware of the filesystem usage on the drive. I think there might be a fundamental misunderstanding of how CloudDrive operates here. DrivePool for example does show that with the local drives. Further I find the graph for the CloudDrive not very useful if you don´t know how much space is taken. Currently I have to check manually how much data is already stored there. It would be great to see in the UI how much of the given CloudDrive I have created is actually still free and at which point I have to create another one or increase the existing. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |