![]() ![]()
The second alternative mentioned is proving the fastest and most reliable for me, Exporting/Importing WSL 2 to move it to another disk. Ideally, even the WSL partition/volume size should shrink and grow with available space on the host in a somewhat timely fashion. That is, the WSL2 file system shouldn't feel like it was a static volume bound to a file on the host (although it is). I think you really want an experience that is as close to that of WSL1 as possible, but with the incredible perf and compat gains, of course. What is the use of a limit that exceeds that of the host (unless actual magic is involved)? Also, artificially limiting the maximum size to a fraction of that of the host seems a bit unnecessary. ![]() COMPRESS YOUR OS DRIVE DISK CLEANUP UNDO WINDOWSThe default partition size should have some connection to the size of the Windows host partition. A periodic background task that did this is really needed (and even better if it could be done online, of course). When I did this, it seemed like I first had to run sudo fstrim / in WSL to get a significant saving (14GB reclaimed with 8GB in use). In Home you don't even have the Optimize-VHD cmdlet, but thankfully (the slightly clumsier) diskpart command which can also be used to compact the. Not really worth the time either since that entire process would probably take about 30 minutes, but compacting is usually under 3. It would probably be fine for my desktop, but not really an option for my laptop. Not even sure if this is possible, but if it is,
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |