Path: ...!eternal-september.org!feeder3.eternal-september.org!news.eternal-september.org!eternal-september.org!.POSTED!not-for-mail
From: Paul <nospam@needed.invalid>
Newsgroups: alt.comp.os.windows-11,comp.os.linux.advocacy
Subject: Re: This Is Why They Say Windows Is A Great OS -- If Your Time Is
 Worth Nothing
Date: Fri, 3 Jan 2025 15:38:32 -0500
Organization: A noiseless patient Spider
Lines: 39
Message-ID: <vl9hs8$2hs6$1@dont-email.me>
References: <vl1ff6$2c41l$1@dont-email.me>
 <8bk8njhp31eu4pri07cppsk95sfkcrtr2h@4ax.com>
 <sycdP.195039$ZAue.171799@fx12.iad> <vl450i$2tjip$2@dont-email.me>
 <o26bnjt79jdmu8nn810b9cit5rvrvl2pc8@4ax.com>
 <ltm1vgFhvukU1@mid.individual.net> <a5ldP.24351$DPp5.18598@fx01.iad>
 <vl56g9$36l6t$1@dont-email.me> <EVwdP.318140$%aWb.223464@fx18.iad>
 <lto7b9Frr0kU2@mid.individual.net> <KjCdP.414705$bYV2.181660@fx17.iad>
 <ltouidF1d8hU1@mid.individual.net> <OAIdP.38926$vfee.7142@fx45.iad>
 <vl8kf0$3t53g$1@dont-email.me> <ltqvbvFbjgeU1@mid.individual.net>
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit
Injection-Date: Fri, 03 Jan 2025 21:38:32 +0100 (CET)
Injection-Info: dont-email.me; posting-host="9732b1a4922fcd0d4c7b33df90a0806a";
	logging-data="83846"; mail-complaints-to="abuse@eternal-september.org";	posting-account="U2FsdGVkX1/CD5asXR6p7UBltX1V7TMqPNLfWWWyXHw="
User-Agent: Ratcatcher/2.0.0.25 (Windows/20130802)
Cancel-Lock: sha1:pYCCZhaJdkKWpd0i47QOrbNUDGQ=
In-Reply-To: <ltqvbvFbjgeU1@mid.individual.net>
Content-Language: en-US
Bytes: 2884

On Fri, 1/3/2025 3:24 PM, rbowman wrote:
> On Fri, 3 Jan 2025 07:16:32 -0500, Paul wrote:
> 
>> My Linux container "ext4.vhdx" is currently 8GB in size.
> 
> I haven't fired up a WSL instance in a while but iirc the reported size 
> seemed to be much larger than what was being used. It worked so I never 
> dug into it. 
> 

From my notes file, and specific for perhaps, a WSL2 install.

optimize-vhd -Path .\ext4.vhdx -Mode full

https://learn.microsoft.com/en-us/windows/wsl/disk-space

*******

A number of environments have toolage for this sort of thing.
The most impressive one, was some flavor of VMWare, which
zeros out unused container bits (in the logical sense rather
than the physical sense), then it "compacts" the container as normal.

The more crude procedures, the user is responsible for using
"zerofree" on unmounted partition, or "sdelete64.exe -z" on a drive
letter first, and the compaction tool rebuilds the container,
removing all the zero portions of the partition as it goes.

# Compacting a VHD used under VirtualBox, when VboxManage
# has no support for VHD compaction...
# Zero the white space inside the partition(s) inside the WIN10.vhd first.

diskpart
select vdisk FILE=F:\WIN10.vhd
compact vdisk

*******

   Paul