[Bug 1854982] Re: Lost compatibilty for backup between Ubuntu 19.10 and FreeBSD 12.0
Lazy is not the goal, nor is prematurely cleaning out the bug tracker. After the 2019-12-04 message, it seemed that things were working well, so it seemed to be time for a re-declaration of what we are trying to achieve. It seems this situation was created by a user explicitly running "zfs set dnodesize=auto" or a "zpool create -O dnodesize=auto ..." then trying to send to a dataset that doesn't support large dnodes. The default dataset property is 'legacy'. This is not caused by the pool's "feature@large_dnode" being "enabled", but it being set to "active" because a dataset was told explicitly to use the feature. It takes effort beyond defaults to get into this situation. When using ZFS on Linux is used as a receiver, "cannot receive new filesystem stream: pool must be upgraded to receive this stream", is the error message, which seem more appropriate (tested both 0.7.9 and 0.8.2). The poor error messages experienced in the bug report are due to using FreeBSD's "zfs receive" command, not the ZOL's "zfs send". It would seem that the error message correction needs to be done on the FreeBSD side. There is a project underway called ZFS on FreeBSD (ZOF). It ultimately will allow FreeBSD to compile from the same codebase as ZOL. If it isn't fixed in the current FreeBSD development, it will be incorporated then. That being said, there are feature flags, when enabled and activated by default, would prevent someone from importing the pool's disks using FreeBSD (vs. this bug's send/recv issue). Again, this may get fixed with ZOF, as it is utilized on FreeBSD machines. It would take a new ZFS version to be deployed on FreeBSD. This also occurs if a pool in made on a newer version of ZOL and an imported on a older, less capable version of ZOL. Though cross importing a pool to another OS (or older edition of ZOL) is an semi-advanced scenario, and the mentioned feature matrix would benefit those users. As these are advanced scenarios, I don't know if or when user education should be done. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1854982 Title: Lost compatibilty for backup between Ubuntu 19.10 and FreeBSD 12.0 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/zfs-linux/+bug/1854982/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1854982] Re: Lost compatibilty for backup between Ubuntu 19.10 and FreeBSD 12.0
At this point, does this need a code improvement to avoid this situation for others? If not, this looks like this bug report is ready to be closed/resolved. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1854982 Title: Lost compatibilty for backup between Ubuntu 19.10 and FreeBSD 12.0 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/zfs-linux/+bug/1854982/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1857040] Re: zfs: upstream support for hardware-accelerated encryption
*** This bug is a duplicate of bug 1845018 *** https://bugs.launchpad.net/bugs/1845018 ** This bug has been marked a duplicate of bug 1845018 SIMD broken in 0.8.1 please backport fix, like Debian -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1857040 Title: zfs: upstream support for hardware-accelerated encryption To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1857040/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1857040] Re: zfs: upstream support for hardware-accelerated encryption
I just installed the linux-generic kernel from focal-proposed (5.4.0-12-generic) built 1/21/2020@15:12:29. It still included zfs-kmod version was still 0.8.2-3ubuntu4. After installing zfs-dkms, kmod version was bumped 0.8.2-3ubuntu5. Fletcher_4_bench performance increased 2.7827x (3.3294 biteswap). I don't know the ubuntu kernel build/release process. When does 0.8.2-3ubuntu5 get included into the kernel itself? (BTW upstream 0.8.3 was released yesterday 1/23/2020. 0.8.2-3ubuntu5 will likely be old anyway) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1857040 Title: zfs: upstream support for hardware-accelerated encryption To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1857040/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1860136] [NEW] (focal) Clevis-tpm2 incompatible with provided tpm2-tools 4.x
Public bug reported: On focal: Tpm2-tools is on version 4.x. The clevis-tpm scripts specifically look for 3.x. Tpm2-tools 4.x had a large reassignment of arguments. Code on Clevis master is compatible with both. ** Affects: clevis (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1860136 Title: (focal) Clevis-tpm2 incompatible with provided tpm2-tools 4.x To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/clevis/+bug/1860136/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1857398] Re: ubiquity should support encryption by default with zfsroot, with users able to opt in to running change-key after install
> It is not appropriate to require the user to type a password on every > boot by default; this must be opt-in. My suggestion was not to make EVERYONE use encrypted ZFS with a passphrase, only those who selected an encryption option within Ubiquity. (Perhaps my code was misunderstood as a implementation suggestion instead of a proof of concept for developers.) Having users opt for encryption and password would leave ZFS in parity with other filesystems installed within Ubiquity. I understand the original idea is to transparently force encryption on everyone but not bother them. Not only is there a performance issue, but you could have some really annoyed people if they ever needed to livecd/mount that filesystem and discover the hidden encryption they have to figure out how to work around. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1857398 Title: ubiquity should support encryption by default with zfsroot, with users able to opt in to running change-key after install To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/1857398/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1858966] Re: Ubiquity/zfs/zsys creates MBR table when LiveCD legacy/bios booted
** Also affects: ubiquity (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1858966 Title: Ubiquity/zfs/zsys creates MBR table when LiveCD legacy/bios booted To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/1858966/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1858966] [NEW] Ubiquity/zfs/zsys creates MBR table when LiveCD legacy/bios booted
Public bug reported: Conventionally, ZFS is contained within GPT partitions. While setting up zfs using ubiquity, legacy/bios booted system use MBR partition tables. This is especially problematic since MBR partitions are restricted to 2TB. GPT disks must contain a "Bios_Grub" partition in order to be bootable from Bios/Legacy systems. This partition can be created using the command "sgdisk -a1 -n1:256K:+768K -t1:EF02 ", where all the 1's in that command specify an available partition number. ** Affects: zfs-linux (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1858966 Title: Ubiquity/zfs/zsys creates MBR table when LiveCD legacy/bios booted To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/zfs-linux/+bug/1858966/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1857398] Re: ubiquity should support encryption by default with zfsroot, with users able to opt in to running change-key after install
FWIW: Running Ubiquity 20.04 with a modified "zsys-setup" configuration
file that manually incorporates a password and encryption pool
properties works great.
echo | zpool create -f \
-O encryption=aes-256-gcm \
-O keylocation=prompt \
-O keyformat=passphrase \
..
-O mountpoint=/ -R "${target}" rpool "${partrpool}"
This works especially well now that the "plymouth ask-for-password" is
working.
Though a known password file would allow an autounlock mechanism until
the change-key is done, I believe it would be rather trivial to have
Ubiquity collect a password from the user, use "-O keylocation=prompt"
and to expect the user to provide the password every reboot.
The performance penalty and the potential for a misguided perception of
security from encrypting everything yet "leaving the key in the handle
until you rekey" seems to be a much.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1857398
Title:
ubiquity should support encryption by default with zfsroot, with users
able to opt in to running change-key after install
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/1857398/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1852406] Re: Double-escape in initramfs DECRYPT_CMD
I believe you ran into something reported and fixed upstream. https://github.com/zfsonlinux/zfs/pull/9202 (Merged to master Aug 27 and included in 0.8.2) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1852406 Title: Double-escape in initramfs DECRYPT_CMD To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/zfs-linux/+bug/1852406/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1845018] Re: SIMD broken in 0.8.1 please backport fix, like Debian
Just needed to add that this cherry-pick has been found to be a problem. Where it has been implemented, it has been retracted. Issue: https://github.com/zfsonlinux/zfs/issues/9346 Issue: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=940932 Debian retraction 0.8.2-1 (unstable), also in 0.8.2-2 (backports) https://tracker.debian.org/news/1068877/accepted-zfs-linux-082-2bpo101-source-amd64-all-into-buster-backports/ Although, this certain cherry-pick shouldn't be used, this launchpad bug should remain open because the lack of SIMD functionality hurts ZFS performance. When a corrected fix is released, it should be considered for backport to 19.10. ** Bug watch added: Github Issue Tracker for ZFS #9346 https://github.com/zfsonlinux/zfs/issues/9346 ** Bug watch added: Debian Bug tracker #940932 https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=940932 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1845018 Title: SIMD broken in 0.8.1 please backport fix, like Debian To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/zfs-linux/+bug/1845018/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1845018] [NEW] SIMD broken in 0.8.1 please backport fix, like Debian
Public bug reported: Eoan Ermine is using 0.8.1. On the current LiveCD, ZFS uses scalar instead of hardware accelerated SIMD instructions. As of zfs-linux 0.8.1-3 (unstable) and 0.8.1-4~bpo10+1 (buster- backports), Debian has "Cherry-pick e5db313 to fix the linux-SIMD compatibility" (https://tracker.debian.org/news/1065134/accepted-zfs- linux-081-4bpo101-source-amd64-all-into-buster-backports-buster- backports/). This fix will be included in 0.8.2, don't expect expect Eoan Ermine to move to that release. ** Affects: zfs-linux (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1845018 Title: SIMD broken in 0.8.1 please backport fix, like Debian To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/zfs-linux/+bug/1845018/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1788776] Re: Ubuntu 18.04 samba/samb-vfs-module not compiled/built --with-acl-support or zfsacl vfs module
ZFS does not, as of this comment, have nfs4acl support under Linux. It is REALLY close. https://github.com/zfsonlinux/zfs/pull/7728 This pull request is mature and just missing test cases for the zfsonlinux build bots. I found this bug report after building ZOL with this pull code and running into the same issues. Going forward, I also ask for Samba to be built ready to support zfsacl. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1788776 Title: Ubuntu 18.04 samba/samb-vfs-module not compiled/built --with-acl- support or zfsacl vfs module To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/samba/+bug/1788776/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1734172] Re: Upgrade ZFS to 0.7.3
Version bump? zfsonlinux 0.7.6 released. https://github.com/zfsonlinux/zfs/releases/tag/zfs-0.7.6 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1734172 Title: Upgrade ZFS to 0.7.3 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/zfs-linux/+bug/1734172/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 279635] Re: Sound doesn't work in firefox
Is "sound" from flash? I was having the same issue. I solved it by doing the following: http://ubuntuforums.org/showthread.php?t=866965 Trust me, there are MANY people here more knowledgeable than me, but this might be a good place to start. (This is probably a duplicate) -- Sound doesn't work in firefox https://bugs.launchpad.net/bugs/279635 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 274085] Re: Please update Ekiga to 3.00
I've also been waiting years and believe this is a MAJOR contribution to linux. I can convince MANY people to give Ubuntu a try once videoconferencing reaches quality levels equivalent to other applications/devices. Congrats and Thanks! -- Please update Ekiga to 3.00 https://bugs.launchpad.net/bugs/274085 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 225480] Re: No option to connect to WebDav(HTTPS)
*** This bug is a duplicate of bug 222532 *** https://bugs.launchpad.net/bugs/222532 Just found bug #222532. This one as a duplicate. ** This bug has been marked a duplicate of bug 222532 Option to connect to "secure webdav" network locations missing in nautilus -- No option to connect to WebDav(HTTPS) https://bugs.launchpad.net/bugs/225480 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 222532] Re: Option to connect to "secure webdav" network locations missing in nautilus
I started bug #225480. It is a duplicate of this and have marked it as such, but I did have something else to add to this: I tried to play around with the "Custom Location" service type and now I know there is something wrong. Here's what I found when I put in various URIs: http://xx.com/users/myaccount -> Firefox opens and asks for authentication, followed by web interface. https://xx.com/users/myaccount -> Same behavior as http dav://xx.com/users/myaccount -> "Can't display location "dav://xx.com/users/myaccount" HTTP Error: Moved Temporarily" davs://xx.com/users/myaccount -> Nautilius prompts for User/Pass, then says "Can't display location "dav://xx.com/users/myaccount" HTTP Error:Not Found" BUT! a network folder is mounted (appears on desktop and under places in Nautilus) named "WebDAV on xx.com" and clicking on it opens a properly usable net folder. -- Option to connect to "secure webdav" network locations missing in nautilus https://bugs.launchpad.net/bugs/222532 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 225480] Re: No option to connect to WebDav(HTTPS)
Oh.. and I forgot to state that I am running version 1:2.22.2-0ubuntu4. -- No option to connect to WebDav(HTTPS) https://bugs.launchpad.net/bugs/225480 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 225480] Re: No option to connect to WebDav(HTTPS)
Thanks for your comments. I am looking for the return of the WebDav(HTTPS) option in the dropdown menu that is found in the image above. It was there in Gusty and worked properly for me. I tried to play around with the "Custom Location" service type and now I know there is something wrong. Here's what I found when I put in various URIs: http://xx.com/users/myaccount -> Firefox opens and asks for authentication, followed by web interface. https://xx.com/users/myaccount -> Same behavior as http dav://xx.com/users/myaccount -> "Can't display location "dav://xx.com/users/myaccount" HTTP Error: Moved Temporarily" davs://xx.com/users/myaccount -> Nautilius prompts for User/Pass, then says "Can't display location "dav://xx.com/users/myaccount" HTTP Error:Not Found" BUT! a network folder is mounted (appears on desktop and under places in Nautilus) named "WebDAV on xx.com" and clicking on it opens a properly usable net folder. What else can I do to help you guys out? -- No option to connect to WebDav(HTTPS) https://bugs.launchpad.net/bugs/225480 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 212418] Re: synaptic package manager deinstalled firefox 3
*** This bug is a duplicate of bug 212416 *** https://bugs.launchpad.net/bugs/212416 Same here. Synaptic: Mark firefox-3.0 Wants to remove xulrunner-1.9 Mark Complains "Depends:xulrunner-1.9:but it is not going to be installed" Close Pre-removing xulrunner doesn't help either -- synaptic package manager deinstalled firefox 3 https://bugs.launchpad.net/bugs/212418 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
