[go: up one dir, main page]
Skip to content
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.

Sign up for GitHub

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

Jump to bottom

WSL Sparse does not work at all. #12103

Open
1 of 2 tasks
PeterTucker opened this issue Sep 29, 2024 · 5 comments
Open
1 of 2 tasks

WSL Sparse does not work at all. #12103

PeterTucker opened this issue Sep 29, 2024 · 5 comments
Labels
question

Comments

@PeterTucker
Copy link

Windows Version

Microsoft Windows [Version 10.0.19045.4894]

WSL Version

2.2.4.0

Are you using WSL 1 or WSL 2?

  • WSL 2
  • WSL 1

Kernel Version

5.15.153.1-microsoft-standard-WSL2

Distro Version

Ubuntu 22.04

Other Software

No response

Repro Steps

Sparse does not work.

Ubuntu disk space (.vhdx file) shows 118gbs in windows 10.
In Ubuntu: /ncdu / --exclude /mnt shows 64gbs

Powershell(admin): notepad "$env:USERPROFILE/.wslconfig"
.wslconfig:

[experimental]
sparseVhd=true

Powershell(admin):

wsl --list # list distros
wsl --manage <distro> --set-sparse true # enable sparse on vdisk
wsl --shutdown # restart wsl
wsl # restart wsl

Then when I check the size, it has not changed at all, still 118gbs.

SOLUTION (MANUAL SHRINKING):

for anyone who finds this in the future. Here is a way to resize the disk manually.

Powershell (admin):

FIRST BACKUP YOUR VHDX FILE
wsl --list # list distros
wsl --shutdown # Be patient and wait a bit for wsl to shutdown. It will eventually shutdown.
wsl --manage <DISTRO_NAME> --set-sparse false
optimize-vhd -Path "<VHDX_FILE>" -Mode full
wsl --manage <DISTRO_NAME> --set-sparse true

Then test if the VHDX file (wiztree) has shrunk and your distro can run.

Expected Behavior

Reclaim disk space in Windows 10.

Actual Behavior

The sparseVhd setting does not reclaim disk space in Windows 10.

Diagnostic Logs

No response
@github-actions GitHub Actions
Copy link

Logs are required for review from WSL team

If this a feature request, please reply with '/feature'. If this is a question, reply with '/question'.
Otherwise please attach logs by following the instructions below, your issue will not be reviewed unless they are added. These logs will help us understand what is going on in your machine.

How to collect WSL logs

Download and execute collect-wsl-logs.ps1 in an administrative powershell prompt:

Invoke-WebRequest -UseBasicParsing "https://raw.githubusercontent.com/microsoft/WSL/master/diagnostics/collect-wsl-logs.ps1" -OutFile collect-wsl-logs.ps1
Set-ExecutionPolicy Bypass -Scope Process -Force
.\collect-wsl-logs.ps1

The script will output the path of the log file once done.

If this is a networking issue, please use collect-networking-logs.ps1, following the instructions here

Once completed please upload the output files to this Github issue.

Click here for more info on logging
If you choose to email these logs instead of attaching to the bug, please send them to wsl-gh-logs@microsoft.com with the number of the github issue in the subject, and in the message a link to your comment in the github issue and reply with '/emailed-logs'.

View similar issues

Please view the issues below to see if they solve your problem, and if the issue describes your problem please consider closing this one and thumbs upping the other issue to help us prioritize it!

Open similar issues:

Closed similar issues:

Note: You can give me feedback by thumbs upping or thumbs downing this comment.

@PeterTucker
Copy link
Author

/question

@PeterTucker
Copy link
Author

Why does it not work?

@github-actions GitHub Actions
Copy link
Diagnostic information 
Found '/question', adding tag 'question'

@elsaco
Copy link
elsaco commented Sep 30, 2024

@PeterTucker after wsl --manage <DISTRO_NAME> --set-sparse false do a wsl --shutdown again, and it should work.

Notice the FileSize before and after running the command:

PS C:\Users\elsaco> Get-VHD -Path "G:\vms\sid\ext4.vhdx"

ComputerName            : ELEVEN
Path                    : G:\vms\sid\ext4.vhdx
VhdFormat               : VHDX
VhdType                 : Dynamic
FileSize                : 1081081856
Size                    : 549453824000
MinimumSize             :
LogicalSectorSize       : 512
PhysicalSectorSize      : 4096
BlockSize               : 1048576
ParentPath              :
DiskIdentifier          : 40545B0A-6EE6-483B-AE7D-B64B4EF39DB1
FragmentationPercentage : 100
Alignment               : 1
Attached                : False
DiskNumber              :
IsPMEMCompatible        : False
AddressAbstractionType  : None
Number                  :

PS C:\Users\elsaco> Optimize-VHD -Path "G:\vms\sid\ext4.vhdx" -Mode full
PS C:\Users\elsaco> Get-VHD -Path "G:\vms\sid\ext4.vhdx"

ComputerName            : ELEVEN
Path                    : G:\vms\sid\ext4.vhdx
VhdFormat               : VHDX
VhdType                 : Dynamic
FileSize                : 1067450368
Size                    : 549453824000
MinimumSize             :
LogicalSectorSize       : 512
PhysicalSectorSize      : 4096
BlockSize               : 1048576
ParentPath              :
DiskIdentifier          : 40545B0A-6EE6-483B-AE7D-B64B4EF39DB1
FragmentationPercentage : 100
Alignment               : 1
Attached                : False
DiskNumber              :
IsPMEMCompatible        : False
AddressAbstractionType  : None
Number

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
question
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@PeterTucker @elsaco