Here we go!
This is the partition table at first boot
root@volumio:/home/volumio# parted /dev/mmcblk0 print
Model: SD USDU1 (sd/mmc)
Disk /dev/mmcblk0: 15.8GB
Sector size (logical/physical): 512B/512B
Partition Table: msdos
Disk Flags:
Number Start End Size Type File system Flags
1 512B 64.0MB 64.0MB primary fat32 boot, lba
2 64.0MB 2500MB 2436MB primary ext4
3 2500MB 15.8GB 13.3GB primary ext4
So the partition has been resized, but
Filesystem Size Used Avail Use% Mounted on
/dev/mmcblk0p2 2.2G 588M 1.5G 29% /imgpart
/dev/loop0 294M 294M 0 100% /static
overlay 262M 14M 228M 6% /
so the resize2fs has not been run.
I can’t directly resize mmcblock0p3, it is failing
root@volumio:/# resize2fs /dev/mmcblk0p3
resize2fs 1.42.12 (29-Aug-2014)
resize2fs: Device or resource busy while trying to open /dev/mmcblk0p3
Couldn't find valid filesystem superblock.
but I can mount it and then resize it (weird, I know)
root@volumio:/# mount /dev/mmcblk0p3 /tmp
root@volumio:/# ls /tmp/
dyn lost+found union work
root@volumio:/# resize2fs /dev/mmcblk0p3
resize2fs 1.42.12 (29-Aug-2014)
Filesystem at /dev/mmcblk0p3 is mounted on /tmp; on-line resizing required
old_desc_blocks = 1, new_desc_blocks = 2
The filesystem on /dev/mmcblk0p3 is now 3256016 (4k) blocks long.
root@volumio:/# umount /tmp
root@volumio:/# df -h
Filesystem Size Used Avail Use% Mounted on
/dev/mmcblk0p2 2.2G 588M 1.5G 29% /imgpart
/dev/loop0 294M 294M 0 100% /static
overlay 13G 143M 12G 2% /
Sorted
I don’t have time to investigate why the partition is resized, but the FS is not, sorry