unresolved free space/capacity in volume properties on windows

[efim.d...@gmail.com]

Hi,

I set capacity for my virtual file system to 1 PB. However free space and capacity never get resolved in the Properties dialog. I can only make it work if capacity does not exceed 100*10^12 bytes (~90TB). I am still on WinFSP 2019.1 though. Any thoughts?

Thank you.

static NTSTATUS GetVolumeInfo(FSP_FILE_SYSTEM *FileSystem, FSP_FSCTL_VOLUME_INFO *VolumeInfo) {

...

    VolumeInfo->TotalSize = 1024LL * 1024LL * 1024LL * 1024LL * 1024LL; // 1 PB

...

[efim.d...@gmail.com]

here is the snapshot of Properties unresolved

[Bill Zissimopoulos]

I do not have a good answer for why this may happen.

 

There is no hard limit on WinFsp on how large a file system may be. However there may be other factors that limit the actual file system size. Or this may be just a problem with Explorer.

 

• Does the file system work correctly otherwise?
• What does the command `fsutil volume diskfree K:` (where K: is your drive) report?

 

Bill

--
You received this message because you are subscribed to the Google Groups "WinFsp" group.
To unsubscribe from this group and stop receiving emails from it, send an email to winfsp+un...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/winfsp/b4113285-999d-4d76-a166-be1fed688282n%40googlegroups.com.

[Bill Zissimopoulos]

The fsutil output shows that the size of the file system is reported correctly.

 

(The error "the volume does not contain a recognized file system" should not be a problem. A WinFsp file system will not be recognized by fsutil, which likely only knows about NTFS, FAT and ReFS.)

 

The problem with Explorer is likely this (please note that this is just speculation on my part): when Explorer sees a very large volume size, it tries to interrogate what it thinks is the underlying media hardware for more information. It likely does this by issuing some storage specific IOCTL that WinFsp does not support, because it is a file system and not a storage driver. Nevertheless it might be worth figuring this out and changing WinFsp so that it correctly supports this scenario.

 

Please consider using FileSpy (http://www.zezula.net/en/fstools/filespy.html) to log file system activity. We may be able to find out what Explorer is doing from FileSpy logs.

 

Bill

 

 

From: Efim Dyadkin <efim.d...@gmail.com>
Sent: Friday, November 27, 2020 4:43 PM
To: Bill Zissimopoulos <bill...@navimatics.com>
Subject: Re: [winfsp] unresolved free space/capacity in volume properties on windows

 

yes, the file system works correctly. 

Here is the output for the fsutil:

C:\>fsutil volume diskfree K:
Error:  The volume does not contain a recognized file system.
Please make sure that all required file system drivers are loaded and that the volume is not corrupted.
A local NTFS volume is required for this operation.
Total free bytes        : 1,125,899,137,880,064 (1024.0 TB)
Total bytes             : 1,125,899,906,842,624 (   1.0 PB)
Total quota free bytes  : 1,125,899,137,880,064 (1024.0 TB)

 

The numbers are as expected.

 

Efim