@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 multipl
@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
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 but
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 tog
Public bug reported:
~2 weeks ago a bug was detected which can lead to data corruption on zfs
pools.
most important:
https://github.com/openzfs/zfs/issues/15526 which has over 300 comments by now
https://github.com/openzfs/zfs/issues/15533
This is bad enough, but a lot of work was done by the de
@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 2
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. Als
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
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 t
Public bug reported:
As explained here: https://github.com/openzfs/zfs/issues/16621
I still run into this bug. This has been fixed with zfs-2.2.7 over a month ago.
So while this is not as severe as the zfs file system corruption bug that was
in 2.2.0,
having a ZFS stack traces in the system log
** Summary changed:
- dmsg stack trace because zfs_log.c bug => upgrade to 2.2.7
+ dmsg stack trace because of zfs_log.c bug => upgrade to 2.2.7
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to zfs-linux in Ubuntu.
https://bugs.launchpad.n
11 matches
Mail list logo
