Public bug reported:
I have often problems with zfsutils-linux updates. I have in a Virtualbox VM a
dual boot from two disks,
- one from ext4 (sda), the one with the failing update and
- another one from zfs (sdb).
The whole update process is far from robust, any fly on the road causes a car
crash.
Why do datapools, that have nothing to do with the update itself, influence the
update.
Last week another update failed because there were somewhere apparently empty
directories.
Please avoid the dependencies on the whole zfs-world, if I want to update 2 or
3 packages in an ext4 system.
The attachment show a re-update try-out, forced through the apt remove of a
non-existing package. It contains:
- the second failed update
- zpool status, that show your new rpool of your standard zfs boot, installed
yesterday
ProblemType: Bug
DistroRelease: Ubuntu 19.10
Package: zfsutils-linux 0.8.1-1ubuntu13
ProcVersionSignature: Ubuntu 5.3.0-13.14-generic 5.3.0
Uname: Linux 5.3.0-13-generic x86_64
NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
ApportVersion: 2.20.11-0ubuntu7
Architecture: amd64
CurrentDesktop: ubuntu:GNOME
Date: Wed Oct 9 18:28:17 2019
InstallationDate: Installed on 2019-04-26 (166 days ago)
InstallationMedia: Ubuntu 19.10 "Eoan EANIMAL" - Alpha amd64 (20190425)
SourcePackage: zfs-linux
UpgradeStatus: No upgrade log present (probably fresh install)
modified.conffile..etc.sudoers.d.zfs: [inaccessible: [Errno 13] Permission
denied: '/etc/sudoers.d/zfs']
** Affects: zfs-linux (Ubuntu)
Importance: Undecided
Status: New
** Tags: amd64 apport-bug eoan
** Attachment added: "zfs-update-fails"
https://bugs.launchpad.net/bugs/1847548/+attachment/5296080/+files/zfs-update-fails
--
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/1847548
Title:
Update of zfs-linux fails
Status in zfs-linux package in Ubuntu:
New
Bug description:
I have often problems with zfsutils-linux updates. I have in a Virtualbox VM
a dual boot from two disks,
- one from ext4 (sda), the one with the failing update and
- another one from zfs (sdb).
The whole update process is far from robust, any fly on the road causes a car
crash.
Why do datapools, that have nothing to do with the update itself, influence
the update.
Last week another update failed because there were somewhere apparently empty
directories.
Please avoid the dependencies on the whole zfs-world, if I want to update 2
or 3 packages in an ext4 system.
The attachment show a re-update try-out, forced through the apt remove of a
non-existing package. It contains:
- the second failed update
- zpool status, that show your new rpool of your standard zfs boot, installed
yesterday
ProblemType: Bug
DistroRelease: Ubuntu 19.10
Package: zfsutils-linux 0.8.1-1ubuntu13
ProcVersionSignature: Ubuntu 5.3.0-13.14-generic 5.3.0
Uname: Linux 5.3.0-13-generic x86_64
NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
ApportVersion: 2.20.11-0ubuntu7
Architecture: amd64
CurrentDesktop: ubuntu:GNOME
Date: Wed Oct 9 18:28:17 2019
InstallationDate: Installed on 2019-04-26 (166 days ago)
InstallationMedia: Ubuntu 19.10 "Eoan EANIMAL" - Alpha amd64 (20190425)
SourcePackage: zfs-linux
UpgradeStatus: No upgrade log present (probably fresh install)
modified.conffile..etc.sudoers.d.zfs: [inaccessible: [Errno 13] Permission
denied: '/etc/sudoers.d/zfs']
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/zfs-linux/+bug/1847548/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : [email protected]
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
