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 dno
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 Kernel
Packages, which is subscribed to zfs-linux in Ubuntu.
https://bugs
*** 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 Kernel
Packages, which is s
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 bitesw
> 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 impleme
** Also affects: ubiquity (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/1858966
Title:
Ubiquity/zfs/zsys creates MBR table when
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 orde
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
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 Kernel
Packages, which is subscribed to zfs-linux in Ubuntu.
https://bugs.la
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
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://tra
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 Kernel
Packages, which is subscribed to zfs-linux in Ubuntu.
https://bugs.launchpad.net/bugs/1734172
Title:
Upgrade ZFS to 0.7.3
12 matches
Mail list logo
