This bug is awaiting verification that the kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed- bionic' to 'verification-done-bionic'. If the problem still exists, change the tag 'verification-needed-bionic' to 'verification-failed- bionic'.
If verification is not done by 5 working days from today, this fix will be dropped from the source code, and this bug will be closed. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Thank you! ** Tags added: verification-needed-bionic -- 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/1759848 Title: Allow multiple mounts of zfs datasets Status in linux package in Ubuntu: Fix Released Status in zfs-linux package in Ubuntu: Fix Released Status in linux source package in Xenial: Fix Released Status in zfs-linux source package in Xenial: Fix Released Status in linux source package in Bionic: Fix Released Status in zfs-linux source package in Bionic: Fix Released Bug description: === SRU Justification, Xenial == An attempt to mount an already mounted zfs dataset should return a new mount referencing the existing super block, but instead it returns an error. Operations such as bind mounts and unsharing mount namespaces create new mounts for the sb, which can cause operations to fail which involve unmounting and remounting the dataset. == Fix == Backport of upstream fix https://trello.com/c/l89Ygj28/352-allow- multiple-mounts-of-zfs-datasets to allow multiple mounts This fix from Seth addresses this issue == Regression potential == Like all backports, this has a potential to be incorrectly backported and break the ZFS mounting. However, any breakage should be picked up via the ZFS smoke tests that thoroughly exercise mounting/dismounting options. At worst, the mounting won't work, but this has been tested, so I doubt this is a possibility. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1759848/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
