Hello RobertCNelson,
Thank you for pointing me there! There seems to be a regression?
With am335x-debian-11.5-minimal-armhf-2022-11-01-2gb.img.xz (Debian 11 newest monthly) from Debian 11.x (Bullseye) - Monthly Snapshots, there is 1.7G space on /dev/mmcblk0p1:
> df -h
Filesystem Size Used Avail Use% Mounted on
udev 214M 0 214M 0% /dev
tmpfs 49M 1.4M 47M 3% /run
/dev/mmcblk0p1 1.7G 836M 790M 52% /
tmpfs 242M 0 242M 0% /dev/shm
tmpfs 5.0M 0 5.0M 0% /run/lock
tmpfs 49M 0 49M 0% /run/user/1000
With bone-debian-10.13-iot-armhf-2022-11-01-4gb.img.xz (Debian 10 newest monthly) from Debian 10.x (Buster) - Monthly Snapshots, there is 3.4G space on /dev/mmcblk0p1:
> df -h
Filesystem Size Used Avail Use% Mounted on
udev 214M 0 214M 0% /dev
tmpfs 49M 1.7M 47M 4% /run
/dev/mmcblk0p1 3.4G 1.9G 1.4G 58% /
tmpfs 242M 0 242M 0% /dev/shm
tmpfs 5.0M 4.0K 5.0M 1% /run/lock
tmpfs 242M 0 242M 0% /sys/fs/cgroup
tmpfs 49M 0 49M 0% /run/user/1000
With AM3358 Debian 10.3 2020-04-06 4GB SD IoT (old) from BeagleBoard.org - latest-images, there is 3.4G space on /dev/mmcblk0p1:
> df -h
Filesystem Size Used Avail Use% Mounted on
udev 215M 0 215M 0% /dev
tmpfs 49M 1.6M 47M 4% /run
/dev/mmcblk0p1 3.4G 1.9G 1.4G 57% /
tmpfs 242M 0 242M 0% /dev/shm
tmpfs 5.0M 4.0K 5.0M 1% /run/lock
tmpfs 242M 0 242M 0% /sys/fs/cgroup
tmpfs 49M 0 49M 0% /run/user/1000
The thing is, this is the same BeagleBone Black. Why does the 11.5 image see half the space available?