-
Notifications
You must be signed in to change notification settings - Fork 841
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Incorrect wsl disk space #5335
Comments
/dev/sdb is not your C drive, it's a VHD that contains your root filesystem. |
Yes, but there should be as much space on it as there is on the current drive, isn’t it? |
No, because it isn't your drive. There is 250GiB on "it" (by default). Where the "it" here isn't a real drive. It is a virtual block device. The size of the virtual device is 250GiB whether the backing storage for the device lives on a 128 gigabyte ssd or a 128 terrabyte raid array. The size isn't real because the device isn't real. |
Where is 250mb here? There 251GB |
@Mystic8b - I don't see MB anywhere in the screenshot you posted, I might be looking at it wrong but I see. /dev/sdb size=251G used=2.8G |
Exactly. Where does 251gb come from? |
Type-o obv. 250 GiB (shows as 251GiB). That number is arbitrary ref #4373. |
Okay, therealkenc edited his post, first he wrote 250mib |
Very normal. You can have a dozen 250 GiB virtual disks (total of 3TiB of space that doesn't really exist) one 128 GiB SSD. [Which is why this is tag by-design already.] |
@therealkenc is right, the disk is dynamic and that is the maximum size. |
Thought of a clearer way to put this. Your ext4 filesystem is ~250GiB. It doesn't resize every time you consume a few more bytes in Windows. |
damn, okay, it seems there is an opportunity to reduce the size of this disk, even so. |
This isn't constructive. |
Steps to reproduce
df -h -> enter
Expected behavior
Free space on wsl corresponds to reality
Actual behavior
Free / occupied space does not correspond to reality
The text was updated successfully, but these errors were encountered: