Hi Michael,
In order to confirm whether we're talking about the same bug here, I tried to reproduce it. Here's what I did:
1) Grab a Focal machine, up-to-date.
2) Run "lxd init" and make sure to choose "zfs" as the backend format for its storage.
3) Fire up a Focal VM using "lxc launch ubuntu-daily:focal fallocate-focal --vm".
4) Shell into the VM, and perform the steps described in the "Steps to reproduce" section from the description.
Here's what I see:
root@fallocate-focal:~# touch foo.img root@fallocate-focal:~# fallocate -z -l 10M foo.img root@fallocate-focal:~# ls -la foo.img -rw-r--r-- 1 root root 10485760 Aug 4 01:02 foo.img
It seems to me that this is working according to what's expected, at least when we consider the fallocate bug that's been originally fixed in Jammy.
Maybe you're experiencing a different problem?
Hi Michael,
In order to confirm whether we're talking about the same bug here, I tried to reproduce it. Here's what I did:
1) Grab a Focal machine, up-to-date.
2) Run "lxd init" and make sure to choose "zfs" as the backend format for its storage.
3) Fire up a Focal VM using "lxc launch ubuntu-daily:focal fallocate-focal --vm".
4) Shell into the VM, and perform the steps described in the "Steps to reproduce" section from the description.
Here's what I see:
root@fallocate- focal:~ # touch foo.img focal:~ # fallocate -z -l 10M foo.img focal:~ # ls -la foo.img
root@fallocate-
root@fallocate-
-rw-r--r-- 1 root root 10485760 Aug 4 01:02 foo.img
It seems to me that this is working according to what's expected, at least when we consider the fallocate bug that's been originally fixed in Jammy.
Maybe you're experiencing a different problem?