| Summary: | ZFS: sysctl "kstat.zfs.POOLNAME.dataset.objset-0xXXXX.dataset_name" not updated when renaming zvols | ||
|---|---|---|---|
| Product: | Base System | Reporter: | Alan Somers <asomers> |
| Component: | kern | Assignee: | Alan Somers <asomers> |
| Status: | Closed FIXED | ||
| Severity: | Affects Only Me | Flags: | asomers:
mfc-stable14+
asomers: mfc-stable13+ asomers: mfc-stable12- |
| Priority: | --- | ||
| Version: | 13.2-RELEASE | ||
| Hardware: | Any | ||
| OS: | Any | ||
| URL: | https://github.com/openzfs/zfs/issues/15482 | ||
|
Description
Alan Somers
2023-11-02 17:10:55 UTC
I've reproduced the issue in a VM. As I suspected, it's caused by renames. But _only_ for zvols. Renaming file systems does not trigger the bug. Steps to Reproduce ================== $ zpool create testpool vtbd1 $ zfs create -V1m testpool/testvol $ sysctl -n kstat.zfs.testpool.dataset.objset-$(printf 0x%x $(zfs get -Hpo value objsetid testpool/testvol)).dataset_name testpool/testvol $ sudo zfs rename testpool/testvol testpool/yyy $ sysctl -n kstat.zfs.testpool.dataset.objset-$(printf 0x%x $(zfs get -Hpo value objsetid testpool/yyy)).dataset_name testpool/testvol The bug affects Linux as well as FreeBSD, so I opened a ticket on github. I opened a PR with OpenZFS. They accepted it and by now the change has been merged into FreeBSD main, stable/14, and stable/13. |