Your message dated Wed, 28 Dec 2022 00:50:07 +0800
with message-id
<CAMr=8w4jptxapgstwz1sivufm77slbjnqjzag_xydqfjo+6...@mail.gmail.com>
and subject line
has caused the Debian Bug report #992001,
regarding zfs-dkms: ZFS_META_GITREV is "unknown"
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact [email protected]
immediately.)
--
992001: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=992001
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: zfs-dkms
Version: 2.0.3-8~bpo10+1
Severity: minor
Dear Maintainer,
I was curious what versions of ZFS I had imported a given pool with, so I asked
zpool history -i, and to my surprise, its log entries had "software version
unknown".
Specifically (note that I believe the entries with "5000/5" were the 0.7.X
behavior, as the commit to change it to report this only landed in 0.8.0):
[...]
2019-10-05.17:12:02 [txg:7593983] open pool version 5000; software version
5000/5; uts steamer 4.19.0-6-amd64 #1 SMP Debian 4.19.67-2+deb10u1 (2019-09-20)
x86_64 [on steamer]
2019-10-05.17:12:03 [txg:7593985] import pool version 5000; software version
5000/5; uts steamer 4.19.0-6-amd64 #1 SMP Debian 4.19.67-2+deb10u1 (2019-09-20)
x86_64 [on steamer]
2019-10-05.17:32:29 [txg:7593993] open pool version 5000; software version
unknown; uts steamer 4.19.0-6-amd64 #1 SMP Debian 4.19.67-2+deb10u1
(2019-09-20) x86_64 [on steamer]
2019-10-05.17:32:30 [txg:7593995] import pool version 5000; software version
unknown; uts steamer 4.19.0-6-amd64 #1 SMP Debian 4.19.67-2+deb10u1
(2019-09-20) x86_64 [on steamer]
2020-01-18.19:19:01 [txg:9253815] open pool version 5000; software version
unknown; uts steamer 4.19.0-6-amd64 #1 SMP Debian 4.19.67-2+deb10u2
(2019-11-11) x86_64 [on steamer]
2020-01-18.19:19:01 [txg:9253817] import pool version 5000; software version
unknown; uts steamer 4.19.0-6-amd64 #1 SMP Debian 4.19.67-2+deb10u2
(2019-11-11) x86_64 [on steamer]
2020-02-18.21:05:14 [txg:9613049] open pool version 5000; software version
unknown; uts steamer 4.19.0-8-amd64 #1 SMP Debian 4.19.98-1 (2020-01-26) x86_64
[on steamer]
[...]
2021-07-12.17:28:29 [txg:16603822] import pool version 5000; software version
unknown; uts steamer 4.19.0-17-amd64 #1 SMP Debian 4.19.194-2 (2021-06-21)
x86_64 [on steamer]
2021-08-01.00:19:47 [txg:16905495] open pool version 5000; software version
unknown; uts steamer 4.19.0-17-amd64 #1 SMP Debian 4.19.194-3 (2021-07-18)
x86_64 [on steamer]
2021-08-01.00:19:47 [txg:16905497] import pool version 5000; software version
unknown; uts steamer 4.19.0-17-amd64 #1 SMP Debian 4.19.194-3 (2021-07-18)
x86_64 [on steamer]
I swapped over from backports-provided 0.8.X to 2.0.X approximately May 15th,
with no change in that output.
(I also just filed a bug upstream about some releases having incorrect values
in include/zfs_gitrev.h - including 2.0.3. Oops.)
A value that conveys the package version (or, at least, the upstream version,
if that's not feasible) would be useful for answering things like "did this
pool ever see X buggy version?" after the fact, perhaps after historical
syslogs are no longer available to infer from module load.
- Rich
-- System Information:
Debian Release: 10.10
APT prefers stable-updates
APT policy: (1000, 'stable-updates'), (1000, 'stable'), (900,
'testing-debug'), (900, 'testing'), (800, 'unstable-debug'), (800, 'unstable'),
(500, 'stable-debug'), (500, 'proposed-updates-debug'), (1, 'experimental')
Architecture: amd64 (x86_64)
Foreign Architectures: i386
Kernel: Linux 4.19.0-17-amd64 (SMP w/16 CPU cores)
Kernel taint flags: TAINT_PROPRIETARY_MODULE, TAINT_OOT_MODULE,
TAINT_UNSIGNED_MODULE
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8),
LANGUAGE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled
Versions of packages zfs-dkms depends on:
ii debconf [debconf-2.0] 1.5.71
ii dkms 2.6.1-4
ii file 1:5.35-4+deb10u2
ii libc6-dev [libc-dev] 2.28-10
ii libpython3-stdlib 3.7.3-1
ii lsb-release 10.2019051400
ii perl 5.28.1-6+deb10u1
ii python3-distutils 3.7.3-1
Versions of packages zfs-dkms recommends:
ii linux-libc-dev 5.10.24-1~bpo10+1
ii zfs-zed 2.0.3-8~bpo10+1
ii zfsutils-linux 2.0.3-8~bpo10+1
Versions of packages zfs-dkms suggests:
ii debhelper 12.1.1
-- debconf information excluded
--- End Message ---
--- Begin Message ---
Source: zfs-linux
Source-Version: 2.1.2-1
This issue should be fixed at least since 2.1.2, please re-open if the
problem persists.
Regards,
Aron
--- End Message ---
