Actually, it may not be an issue even for Jammy HWE. My copy shows block
cloning as an option that's off.
--
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/2044657
Title:
Multiple data
This issue is different. It's another problem with block copy. But
that's known to still be an issue. It's why block copy is disabled in
2.2.1. This is only an issue for the Jammy HWE, which has 2.2.0. No one
should be shipping 2.2.0 with anything. It should be replaced with 2.2.1
at least.
--
FYI everyone, another corruption-with-zeros bug was found (so this issue
was not completely fixed): https://github.com/openzfs/zfs/issues/15933
The fixed was committed last week, and is not yet part of a release:
https://github.com/openzfs/zfs/pull/16019
** Bug watch added:
This bug was fixed in the package zfs-linux - 0.8.3-1ubuntu12.17
---
zfs-linux (0.8.3-1ubuntu12.17) focal; urgency=medium
* Cherry-pick
https://github.com/robn/zfs/commit/f2f7f43a9bf4628328292f25b1663b873f271b1a.patch
backport of "dnode_is_dirty: check dnode and its data
This bug was fixed in the package zfs-linux - 2.1.5-1ubuntu6~22.04.3
---
zfs-linux (2.1.5-1ubuntu6~22.04.3) jammy; urgency=medium
* d/p/77b0c6f0403b2b7d145bf6c244b6acbc757ccdc9.patch Cherry-pick
"dnode_is_dirty: check dnode and its data for dirtiness" fix from
zfs-2.1.14.
Sorry hedrick if a left a wrong impression. Looks, like my comment was
not clear enough, I was recommending the 2.2.2 version for systems which
came with a 2.2.x package, e.g. 23.10 (mantic). There the bugs started
to make real problems (happening much more often) because a bunch of
things came
Since I was just referenced, note that I wouldn't favor putting 2.2 into
Jammy. I would, however, prefer to see the latest 2.1.x.
2.2 is still seeing a substantial number of bug fixes. It will probably
be ok by the release date of 24.04, but I still wouldn't change major
versions for Jammy.
--
I can only second @hedrick on his comment and as already written above,
recommend everyone to build 2.2.2 by yourself. I am running 2.2.2 stable
for a couple of weeks on mantic. I still have to fix one notebook here
which got f**ked up (most likely) by this and reports no errors on a
pool scrub
@xyv41:
As mentioned in the last comment, the fix is only a cherry-pick so the version
will go from 2.1.5-1ubuntu6~22.04.2 to 2.1.5-1ubuntu6~22.04.3 because upgrading
to 2.1.14 would bear the risk that other bugs might get fixed, too.
Regarding the release date: for mantic it took about 7 days
it's likely to take a while. It's been committed but not released. They
chose to cherry pick the patch, so the version will still show as 2.1.5.
A lot of us would prefer going to 2.1.14, but there are enough other
changes that Ubuntu staff didn't want to do it. I'm considering building
my own zfs
I don't get it. The latest ZFS version in Jammy seem to be 2.1.5 and not
2.1.14 nor 2.2.2. When will the committed version with the fix be
available to the general public?
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to zfs-linux in
I struggle to reproduce the issue on focal with v5.4 and
0.8.3-1ubuntu12.16 zfs
but also see no regressions with the proposed 12.17 update.
** Tags removed: verification-needed-focal
** Tags added: verification-done-focal
--
You received this bug notification because you are a member of Kernel
Verification done for jammy-proposed.
TEST CASE:
I did test the -proposed package on a clean install of jammy (without the HWE
kernel) and a test pool.
Since you need a tool that uses lseek SEEK_HOLE/SEEK_DATA and the
coreutils bundled with Ubuntu 22.04 are still at version 8.x, I manually
This bug was fixed in the package zfs-linux - 2.2.0-0ubuntu1~23.10.2
---
zfs-linux (2.2.0-0ubuntu1~23.10.2) mantic; urgency=medium
* d/p/9b9b09f452a469458451c221debfbab944e7f081.patch Cherry-pick
"dnode_is_dirty: check dnode and its data for dirtiness" fix from
zfs-2.2.2.
To add to Jonathan's comment, a slightly easier way to do this (at least
for someone not familiar with bootloaders) is to add `options zfs
zfs_dmu_offset_next_sync=0` to /etc/modprobe.d/zfs.conf
https://openzfs.github.io/openzfs-
docs/Performance%20and%20Tuning/Module%20Parameters.html
On a side
Just updated my pool today and then remembered hearing about this bug.
Guess I should have searched first. Looking forward to the proposed fix
getting released. Thanks for the patch. :)
For now, I'm using the suggestion of setting
`zfs_dmu_offset_next_sync=0` based on this:
@Dimitri If I see it correctly you have been assigned this bug. So I
thought this should be your decision!? If not this is bad, who is
responsible then for the rejection of this? Whoever made that decision
obviously didn´t follow close enough what was going on in the zfs GitHub
repo regarding this
@fl140 i have previously prepared upgrades to new point release from
2.1.x and 2.2.x series all of those SRUs got rejected.
@mfo all dkms based kernel modules that kernel packages prebuild get
picked up every kernel sru cycle, including zfs, which will be picked in
a future kernel sru cycle.
**
@Timo I just saw the 2.2.0-0ubuntu1~23.10.2 announcement for mantic.
IMHO cherry picking is not a very good approach when it comes to 2.2.2.
I followed the ZFS github repo closely during the time of the bug in
November and December until 2.2.2 came out on the ZFS GitHub repo and
there where
So, I did test the -proposed package for mantic on a clean install by
creating a test-pool and running the zhammer.sh linked #16.
…
As expected on an unpatched system the error occurred during the first
iteration:
[zhammer::1858] zhammer_1858_0 differed from zhammer_1858_538!
[zhammer::1858]
Hello Tobias, or anyone else affected,
Accepted zfs-linux into jammy-proposed. The package will build now and
be available at https://launchpad.net/ubuntu/+source/zfs-
linux/2.1.5-1ubuntu6~22.04.3 in a few hours, and then in the -proposed
repository.
Please help us by testing this new package.
Hello Tobias, or anyone else affected,
Accepted zfs-linux into mantic-proposed. The package will build now and
be available at https://launchpad.net/ubuntu/+source/zfs-
linux/2.2.0-0ubuntu1~23.10.2 in a few hours, and then in the -proposed
repository.
Please help us by testing this new package.
For what it's worth, we've been running a file server for several weeks
with the 2.1.14 .ko files in 22.04 with no problem. I didn't try to
cherry pick the one fix as I'd prefer to have the whole 2.1.14.
--
You received this bug notification because you are a member of Kernel
Packages, which is
Reviewed zfs-linux on mantic/jammy/focal-unapproved for acceptance.
They all look good to me (notes below, in addition to usual checks),
but I'll ask for another reviewer to provide input too, as it's ZFS.
(But I did want to provide some assistance in this long-running SRU.)
Thanks,
Mauricio
** Description changed:
[ Impact ]
* Multiple data corruption issues have been identified and fixed in
ZFS. Some of them, at varying real-life reproducibility frequency have
been deterimed to affect very old zfs releases. Recommendation is to
upgrade to 2.2.2 or 2.1.14 or backport
Hey Chris,
> ... the primary way that users get zfs in Ubuntu is via the module built with
> the *kernel* image.
> ... fixing that requires a zfs-linux upload and then a further kernel upload
> to pull in the new zfs.
Yes, fixing the zfs modules shipped with the kernel packages require
** Changed in: zfs-linux (Ubuntu Lunar)
Importance: Medium => Undecided
--
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/2044657
Title:
Multiple data corruption issues in zfs
** Changed in: zfs-linux (Ubuntu Mantic)
Status: Incomplete => In Progress
** Changed in: zfs-linux (Ubuntu Jammy)
Status: Confirmed => In Progress
** Changed in: zfs-linux (Ubuntu Focal)
Status: Confirmed => In Progress
** Changed in: zfs-linux (Ubuntu Lunar)
** Description changed:
[ Impact ]
- * Multiple data corruption issues have been identified and fixed in
+ * Multiple data corruption issues have been identified and fixed in
ZFS. Some of them, at varying real-life reproducibility frequency have
been deterimed to affect very old zfs
** Changed in: zfs-linux (Ubuntu Lunar)
Status: Confirmed => Won't Fix
--
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/2044657
Title:
Multiple data corruption issues in zfs
This is a bit more difficult, because the primary way that users get zfs
in Ubuntu is via the module built with the *kernel* image. My
understanding is that fixing that requires a zfs-linux upload and then a
further kernel upload to pull in the new zfs.
--
You received this bug notification
>Should we quickly do such a minimal backport to get that fix out
quickly
Unequivocally, yes. It has been several weeks and users of ZFS across
multiple releases are still exposed to a data corruption bug. The fix
should go out asap, especially when it's only a single-line fix.
This bug has
Additionally: my understanding is that the corruption fix is minimally
invasive and should be easy to backport. Should we quickly do such a
minimal backport to get that fix out quickly, and then have less
pressure to handle the hardware enablement kernel quickly?
--
You received this bug
So, looking at 2.1.14 in lunar-proposed -
This is not bugfix-only (or even bugfix and hardware-enablement only - it
includes, at least, changes to colourise the output of some commands). Also, I
think this will introduce bug #2046082 into lunar and jammy?
I see we've accepted some ZFS
It looks like there is one person charged with maintaining this package,
and we're still in the holidays. I agree this has taken too long and it
sounds like there should be more resources assigned but I will wait for
Dimitri to finish his work. The Ubuntu ZFS package has quite a few
I have to agree with FL140, it is absolutely shocking that there is not even a
sign of activity here.
Not only is the bug still present in Mantic but also in Jammy (22.04 LTS) which
is the current long-term-support release and supposed to be used in server
environments.
That is absolutely
IMHO it is alarming, that there STILL is no official 2.2.2 package for
Mantic which is the official current release, for a problem which would
have needed real attention and a hotfix. I build my own packages as I
noticed the problem early, but what with all the users out there which
have faith in
@Paul no, it isn't.
--
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/2044657
Title:
Multiple data corruption issues in zfs
Status in zfs-linux package in Ubuntu:
Fix Released
Sorry I can't tell, is the data corruption bug backported into mantic
2.2.0? Or is mantic still not protected?
--
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/2044657
Title:
I am also interested if there will be release for Jammy soon?
--
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/2044657
Title:
Multiple data corruption issues in zfs
Status in
Hi. Will there be a release for Jammy soon?
--
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/2044657
Title:
Multiple data corruption issues in zfs
Status in zfs-linux package in
** Changed in: zfs-linux (Ubuntu Noble)
Status: Fix Committed => Fix Released
--
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/2044657
Title:
Multiple data corruption issues in
On Fri, 8 Dec 2023 at 23:35, Steve Langasek <2044...@bugs.launchpad.net> wrote:
>
> zfs-linux (2.2.2-0ubuntu1~23.10) mantic; urgency=medium
>
> * New upstream release. LP: #2044657
> - Address potential data corruption
>
> I'm assuming the plan for fixing it on earlier releases does not
All good hear, but curious about:
*apt show zfsutils-linux |grep -e "Breaks"
WARNING: apt does not have a stable CLI interface. Use with caution in
scripts.
Breaks: openrc, spl (<< 0.7.9-2), spl-dkms (<< 0.8.0~rc1), zfs-dkms (>>
2.2.2-0ubuntu1...), zfs-dkms (<< 2.2.2-0ubuntu1)
Both live
zfs-linux (2.2.2-0ubuntu1~23.10) mantic; urgency=medium
* New upstream release. LP: #2044657
- Address potential data corruption
I'm assuming the plan for fixing it on earlier releases does not involve
updating to 2.2.2.
And this does not fall under a hardware enablement exception. AND
Wait... I seem to be confused by this:
>>>
mafoelffen@noble-d05:~$ apt-cache show zfsutils-linux | grep 'Package:\|Breaks:'
Package: zfsutils-linux
Breaks: openrc, spl (<< 0.7.9-2), spl-dkms (<< 0.8.0~rc1), zfs-dkms (>>
2.2.2-0ubuntu1...), zfs-dkms (<< 2.2.2-0ubuntu1)
>>>
Does that mean, even
Rick and I have been testing the Proposed 2.2.2 packages in Noble since
yesterday morning. Great so far.
@fl140 --
Thanks you for the link. I'll pass that on.
Waiting to see if anything of this helps with: zfs-dkms
2.1.5-1ubuntu6~22.04.2 https://bugs.launchpad.net/ubuntu/+source/zfs-
Could https://github.com/openzfs/zfs/pull/15651 be picked up for this
update still?
--
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/2044657
Title:
Multiple data corruption issues in
Oh, I missed this bit in https://bugs.launchpad.net/ubuntu/+source/zfs-
linux/+bug/2040181/comments/10 in the other bug:
"It is still worth it to release this sru, before staging the next one
in proposed"
--
You received this bug notification because you are a member of Kernel
Packages, which
https://bugs.launchpad.net/ubuntu/+source/zfs-linux/+bug/2040181
updating mantic to 2.2.0 final is in mantic-proposed, and this bug here
is in mantic-unapproved.
Should we drop 2.2.0 from mantic-proposed in favor of this one here?
--
You received this bug notification because you are a member
FYI The `zdb -ccc` command does NOT show you which files where affected,
but it helped me to identify at least one zpool which got corrupted
between 2.2.0 and 2.2.1, but the source of this has to be investigated
further. At least it can't hurt to see if at least the pool is
consistent (there still
BTW I have the 2.2.2 self built custom package running here on a 23.10
Ubuntu installation and it looks good so far. I would also advice to
check any possible affected pools running `zdb -ccc -vvv pool_name`
(Note: I don't know if the third -c makes any difference found nothing
in the man page.
@mafoelffen I also filed a bug report here, but it looks like it never showed
up anywhere. Anyways, since the 2.2.1 HotFix never made it to mantic and I
needed this fixed ASAP I made a script for building the deb packages, so if you
also like to build your own until there is an official HotFix
@xnox --
Thank you!!!
This is what I see in Noble right now:
>>>
mafoelffen@noble-d05:~$ apt list -a zfsutils-linux
Listing... Done
zfsutils-linux/noble-proposed 2.2.2-0ubuntu1 amd64
zfsutils-linux/noble,now 2.2.1-0ubuntu1 amd64 [installed]
>>>
So it 2.2.1 got pushed to Noble main, with 2.2.2 to
** Changed in: zfs-linux (Ubuntu Mantic)
Status: Confirmed => In Progress
--
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/2044657
Title:
Multiple data corruption issues in zfs
** Description changed:
- OpenZFS linux kernel module currently has multiple potential data
- corruption issues identified to have been present since at least 0.6
- (?!).
+ [ Impact ]
- This bug report will track upgrades to releases 2.2.2, OR 2.1.14, OR
- backport/cherry-pick of dirty dnode
** Changed in: zfs-linux (Ubuntu Mantic)
Importance: Undecided => High
** Changed in: zfs-linux (Ubuntu Lunar)
Importance: Undecided => High
** Changed in: zfs-linux (Ubuntu Jammy)
Importance: Undecided => High
** Changed in: zfs-linux (Ubuntu Focal)
Importance: Undecided => Medium
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: zfs-linux (Ubuntu Mantic)
Status: New => Confirmed
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to zfs-linux in Ubuntu.
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: zfs-linux (Ubuntu Lunar)
Status: New => Confirmed
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to zfs-linux in Ubuntu.
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: zfs-linux (Ubuntu Focal)
Status: New => Confirmed
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to zfs-linux in Ubuntu.
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: zfs-linux (Ubuntu Jammy)
Status: New => Confirmed
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to zfs-linux in Ubuntu.
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: zfs-linux (Ubuntu Xenial)
Status: New => Confirmed
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to zfs-linux in Ubuntu.
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: zfs-linux (Ubuntu Bionic)
Status: New => Confirmed
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to zfs-linux in Ubuntu.
63 matches
Mail list logo
