# zxfer -dFkPv -g 376 -T root@backup.example.com -R tank zdata/home/install/squid Checking grandfather status of all snapshots marked for deletion... Grandfather check passed. Creating destination filesystem "zdata/home/install/squid/tank" with specified properties. cannot create 'zdata/home/install/squid/tank': 'objsetid' is readonly Error when creating destination filesystem. # pkg version -v | g zxfer zxfer-1.1.7 = up-to-date with index # locate zxfer /usr/ports/sysutils/zxfer /usr/ports/sysutils/zxfer/Makefile /usr/ports/sysutils/zxfer/distinfo /usr/ports/sysutils/zxfer/pkg-descr # ll /usr/local/sbin/ | g zxfer -r-xr-xr-x 1 root wheel 80144 Feb 10 12:39 zxfer # uname -a FreeBSD squid.example.com 12.2-RELEASE-p3 FreeBSD 12.2-RELEASE-p3 GENERIC amd64 # Installed from ports. Not sure why this error is happening. I see a reference in Jude's Github that this has been fixed but this still occurs.
I added 'objsetid' to the list of readonly properties as follows: readonly_properties="type,creation,used,available,referenced,\ compressratio,mounted,version,primarycache,secondarycache,\ usedbysnapshots,usedbydataset,usedbychildren,usedbyrefreservation,\ version,volsize,mountpoint,mlslabel,keysource,keystatus,rekeydate,encryption,\ refcompressratio,written,logicalused,logicalreferenced,createtxg,guid,origin,\ filesystem_count,snapshot_count,clones,defer_destroy,receive_resume_token,\ userrefs,objsetid" zxfer no longer complains and happily proceeds to transfer zfs snapshots remotely. The zxfer port should be updated with this minor addition. ~Doug
Maintainer approves
FreshPorts related page, https://www.freshports.org/sysutils/zxfer/ reports: Last Update: 2021-04-06 14:31:07 Commit Hash: 305f148 Could this ticket be closed?
> Could this ticket be closed? Replying to my own question: No, as of today, I still get: "cannot create 'zroot/safe': 'objsetid' is readonly".
The port should definitely be updated as suggested to include objsetid in the list of read only properties. As is no new datasets can be added to zxfer backup jobs using zxfer as documented, because they'll always fail trying to set the read-only objsetid property. As a workaround the property can be ignored by adding "-I objsetid", to the invocations. This a major regression (even if it wasn't caused by zxfer) affecting all zxfer users on all still supported FreeBSD releases.
Maintainer timeout. Upstream approves. Will cherry-pick upstream PR https://github.com/allanjude/zxfer/pull/54 to fix this. @allanjude, perhaps you could make a new release some time?
A commit in branch main references this bug: URL: https://cgit.FreeBSD.org/ports/commit/?id=31efecb9ca20446d19333f8582cc75d623c1fe6c commit 31efecb9ca20446d19333f8582cc75d623c1fe6c Author: Robert Clausecker <fuz@FreeBSD.org> AuthorDate: 2025-02-15 13:54:45 +0000 Commit: Robert Clausecker <fuz@FreeBSD.org> CommitDate: 2025-02-18 14:16:20 +0000 filesystems/zxfer: make property objsetid readonly Approved by: allanjude (upstream) Approved by: ports@scaleengine.com (maintainer timeout) Reported by: dougs@dawnsign.com PR: 253418 MFH: 2025Q1 filesystems/zxfer/Makefile | 7 +++++-- filesystems/zxfer/distinfo | 4 +++- 2 files changed, 8 insertions(+), 3 deletions(-)
A commit in branch 2025Q1 references this bug: URL: https://cgit.FreeBSD.org/ports/commit/?id=b7e251d83df54eb7917dba363c2cfb33116dfbb0 commit b7e251d83df54eb7917dba363c2cfb33116dfbb0 Author: Robert Clausecker <fuz@FreeBSD.org> AuthorDate: 2025-02-15 13:54:45 +0000 Commit: Robert Clausecker <fuz@FreeBSD.org> CommitDate: 2025-02-18 14:29:16 +0000 filesystems/zxfer: make property objsetid readonly Approved by: allanjude (upstream) Approved by: ports@scaleengine.com (maintainer timeout) Reported by: dougs@dawnsign.com PR: 253418 MFH: 2025Q1 (cherry picked from commit 31efecb9ca20446d19333f8582cc75d623c1fe6c) filesystems/zxfer/Makefile | 7 +++++-- filesystems/zxfer/distinfo | 4 +++- 2 files changed, 8 insertions(+), 3 deletions(-)
Thank you for the report. I'm sorry it took so long to get this one addressed.