[Bug] LXCs volumes can't be resized

[JoaGamo]

Hello!
I'm using:
Plugin: MooseFS PVE 0.1.10 (beta)
Proxmox VE 9.0.10

LXCs with a non-block device moosefs mountpoint can't be resized with the Proxmox GUI/plugin. From Proxmox Tasks, I get the error can't resize this image format when I try to resize a container's rootfs/mp0 partition, like this one: rootfs: mooseFS:193/vm-193-disk-0.raw,size=8G.
As recommended in #50 block devices at the moment shouldn't be used for LXCs, so I didn't confirm the issue there.

In the meantime, I did this workaround to resize the container's volume, anyone may find it useful.

// 32G is my target, bigger than my previous 8G volume. I did not try shrinking.
truncate -s 32G /mnt/pve/moosefs/images/193/vm-193-disk-0.raw
losetup -fP /mnt/pve/moosefs/images/193/vm-193-disk-0.raw
// get loop device
losetup -a | grep vm-193-disk-0
// resize it
parted /dev/loopX resizepart 1 100%
e2fsck -f /dev/loopX
resize2fs /dev/loopX
losetup -d /dev/loopX
// in my case, update `size=8G` in /etc/pve/lxc/193.conf value from 8G to size=32G

[Zorlin]

Thanks! Investigating tonight.

[Zorlin]

Fixed

[JoaGamo]

That was fast, nice work and thank you!

[Zorlin]

I'll tag you when we cut the new release with the fix in it @JoaGamo

[JoaGamo]

Hey @Zorlin this was not fixed in v0.11.1, I still get: TASK ERROR: can't resize this image format when resizing a LXC under MooseFS file storage with command pct resize <vmid> rootfs +4G. please re-open the issue

[Zorlin]

Hey @Zorlin this was not fixed in v0.11.1, I still get: TASK ERROR: can't resize this image format when resizing a LXC under MooseFS file storage with command pct resize <vmid> rootfs +4G. please re-open the issue

Apologies. Please provide logs and a scenario for me to replicate and I will test this again and smash it properly this time.

(I probably have enough to go on actually, will try and replicate this weekend)

[JoaGamo]

Understood!
pve-version:

root@gamohosthp:~# pveversion -v
proxmox-ve: 9.1.0 (running kernel: 6.17.2-1-pve)
pve-manager: 9.1.1 (running version: 9.1.1/42db4a6cf33dac83)

Running plugin version pve-moosefs v0.1.11 (beta).

Set up your MooseFS storage in Proxmox (in Proxmox, go to Datacenter -> Storage) under the standard FUSE backend. The problem does not occur with the NBD (Block) backend.
Create a Proxmox LXC with everything default settings. You can do this either through the Web GUI of Proxmox, or use CLI.

For visibility I'll show the command I used with CLI and console logs.

# This creates a Debian 13 LXC, with the rootfs being in a MooseFS mountpoint with size=8GB. 
root@gamohosthp:/# pct create 500 /mnt/pve/gamofs/template/cache/debian-13-standard_13.1-2_amd64.tar.zst --rootfs GamoFS:8
Plugin "PVE::Storage::Custom::MooseFSPlugin" is implementing an older storage API, an upgrade is recommended
Formatting '/mnt/pve/gamofs/images/500/vm-500-disk-0.raw', fmt=raw size=8589934592 preallocation=off
Creating filesystem with 2097152 4k blocks and 524288 inodes
Filesystem UUID: 3b5fae63-a641-4eb9-9e7d-55e9962e67d7
Superblock backups stored on blocks: 
        32768, 98304, 163840, 229376, 294912, 819200, 884736, 1605632
extracting archive '/mnt/pve/gamofs/template/cache/debian-13-standard_13.1-2_amd64.tar.zst'
Total bytes read: 551505920 (526MiB, 155MiB/s)
Detected container architecture: amd64
Creating SSH host key 'ssh_host_ed25519_key' - this may take some time ...
done: SHA256:NqMWvxhuZoJ+TwAbM1kz16RehL7f5EtV2z+5LV4f2fg root@localhost
Creating SSH host key 'ssh_host_ecdsa_key' - this may take some time ...
done: SHA256:YQThMJ7ZbIWVHwirv0fOR6LE3O1LaS5Grwf5MdGl2Xc root@localhost
Creating SSH host key 'ssh_host_rsa_key' - this may take some time ...
done: SHA256:cduMXNxXIASyNxDiyo4KjSh0RR2ns1z2xBGO5tJ+yjo root@localhost

Then, attempt a pct resize. In the previous command, we created a container with vmid=500, so we'll reference it again.

root@gamohosthp:~# pct resize 500 rootfs +4G
Plugin "PVE::Storage::Custom::MooseFSPlugin" is implementing an older storage API, an upgrade is recommended
can't resize this image format

When doing the same steps but with the NBD backend, the resize feature works!. But I found a bug, to not lose track of this issue, I opened a different issue to track the new problem #57

I think you did fix the NBD backend by looking at your commit ;)