The bug was fixed in 2.1.4-0ubuntu0.1 but that version is still in
proposed for Jammy. The current release version still seems to be
2.1.2-1ubuntu3.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to zfs-linux in Ubuntu.
Are there any updates on getting this released into Jammy? We've gotten
several reports of mysql failing due to this issue
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to zfs-linux in Ubuntu.
https://bugs.launchpad.net/bugs/1969247
Ah alright, that's fine then. Hopefully the Jammy version can move from
proposed to release soon.
Thanks!
** Tags removed: verification-failed-jammy
** Tags added: verification-done-jammy
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to
That's fair, it does seem to work when using that method. However, for
this to be an actual fix it needs to work out of the box. Since mysql
still fails to install and fallocate still fails on kinetic after
installing with zfs, it isn't ready for normal users yet
--
You received this bug
Added the apport output of kinetic in its current state to a duplicate
bug: https://pad.lv/1975513
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to zfs-linux in Ubuntu.
https://bugs.launchpad.net/bugs/1969247
Title:
fallocate with
I've done some more testing with Jammy and can confirm this does not
fully fix the issue. I also tried to install mysql on kinetic now that
the fix is 'released' and it still fails. I think more needs to be done
with this to get fallocate working on zfs
** Tags removed: verification-done-jammy
**
** Tags added: verification-done-jammy
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to zfs-linux in Ubuntu.
https://bugs.launchpad.net/bugs/1969247
Title:
fallocate with FALLOC_FL_ZERO_RANGE produces zero-size files on zfs in
Jammy
The update fixed my lxd containers using the same method from above on
my zfs jammy system. However it did not fix the base system itself. When
I try to install mysql-server or run the fallocate test it still fails.
Are there additional steps, other than just apt updating and upgrading,
that I or
zfs-dkms ended up working for me using LXD with the following test case:
sudo add-apt-repository ppa:ci-train-ppa-service/4831
sudo apt update
sudo apt upgrade
sudo apt install zfs-dkms
lxd init
lxc launch images:ubuntu/focal test-mysql
lxc exec test-mysql bash
# apt update && apt dist-upgrade
** Summary changed:
- fallocate produces zero-size files on zfs in Jammy
+ fallocate with FALLOC_FL_ZERO_RANGE produces zero-size files on zfs in Jammy
** Description changed:
- I came across this error when testing various mysql setups in an LXD
- container and managed to reproduce it
)
Status: Confirmed => Invalid
** Changed in: mysql-8.0 (Ubuntu)
Assignee: Lena Voytek (lvoytek) => (unassigned)
** Changed in: zfs-linux (Ubuntu)
Status: New => Confirmed
** Summary changed:
- mysql-server install crashes in LXD container on Jammy host
+ fallocate prod
** Also affects: zfs-linux (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to zfs-linux in Ubuntu.
https://bugs.launchpad.net/bugs/1969247
Title:
mysql-server install crashes in LXD
Looking into the Debian report it seems that this issue can be
reproduced without apache2. Users have reported being able to reproduce
with "Nextcloud PHP on nginx." I will set the apache2 part of this issue
as incomplete for now because it does not seem to be the main cause.
** Changed in:
13 matches
Mail list logo
