Bug 173234 - ZFS: allow filtering of properties on zfs receive
Summary: ZFS: allow filtering of properties on zfs receive
Status: Closed FIXED
Alias: None
Product: Base System
Classification: Unclassified
Component: kern (show other bugs)
Version: 8.3-RELEASE
Hardware: Any Any
: --- Affects Only Me
Assignee: Steven Hartland
URL: https://www.illumos.org/issues/2745
Keywords: feature, needs-qa
Depends on:
Blocks:
 
Reported: 2012-10-31 10:20 UTC by Steven Hartland
Modified: 2024-11-25 10:29 UTC (History)
5 users (show)

See Also:

Attachments
file.txt (21.61 KB, text/plain)
2012-10-31 10:20 UTC, Steven Hartland 		no flags Details
View All Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Steven Hartland 2012-10-31 10:20:01 UTC 
Its some times useful to allow filtering / overriding of zfs properties on receive for example if a disk has a quota set the receive can fail due to changes to the way the data is compressed resulting in exceeding the quota.

The attached patch adds both -x (exclude property) as well as -o (override property) to zfs receive as requested by the upstream ticket:-
https://www.illumos.org/issues/2745

This mirrors and extends the functionality available in Sun's ZFS receive.

Fix: Apply the attached patch

Patch attached with submission follows:
How-To-Repeat: N/A
Comment 1 Mark Linimon freebsd_committer freebsd_triage 2012-11-05 02:37:03 UTC 
Responsible Changed
From-To: freebsd-bugs->freebsd-fs

Over to maintainer(s).
Comment 2 Steven Hartland freebsd_committer freebsd_triage 2012-12-11 14:10:25 UTC 
Responsible Changed
From-To: freebsd-fs->smh

I'll take it.
Comment 3 Ahmed Kamal 2015-07-21 14:13:50 UTC 
Is this merged yet ?
Comment 4 Steven Hartland freebsd_committer freebsd_triage 2015-07-21 14:15:42 UTC 
Afraid not, need to get some time to clean up based on feedback from illumos
Comment 5 Lapo Luchini 2017-02-17 16:13:10 UTC 
Seems that FreeNAS is using this already:
https://bugs.pcbsd.org/issues/11133
Comment 6 Eitan Adler freebsd_committer freebsd_triage 2018-05-28 19:43:49 UTC 
batch change:

For bugs that match the following
-  Status Is In progress 
AND
- Untouched since 2018-01-01.
AND
- Affects Base System OR Documentation

DO:

Reset to open status.


Note:
I did a quick pass but if you are getting this email it might be worthwhile to double check to see if this bug ought to be closed.
Comment 7 Graham Perrin freebsd_committer freebsd_triage 2022-10-17 12:39:23 UTC 
Keyword: 

    patch
or  patch-ready

– in lieu of summary line prefix: 

    [patch]

* bulk change for the keyword
* summary lines may be edited manually (not in bulk). 

Keyword descriptions and search interface: 

    <https://bugs.freebsd.org/bugzilla/describekeywords.cgi>
Comment 8 Graham Perrin 2023-10-17 11:54:55 UTC 
^Triage: 

* make former assignee fs@ a CC recipient
* avoiding tagging summary lines
* severity reduced to the norm for a feature request
* remove deprecated keyword
* add keywords (feature, needs-qa)

With OpenZFS in FreeBSD 13.0 and greater, does there remain a need for this?

If so: an upstream pull request may be more appropriate. 

Thanks
Comment 9 Mark Linimon freebsd_committer freebsd_triage 2024-11-24 05:26:58 UTC 
^Triage: feedback timeout (> 1 year).
Comment 10 Andriy Gapon freebsd_committer freebsd_triage 2024-11-25 10:29:27 UTC 
Just in case, we have actually got the requested features via OpenZFS.
So, the issue has been fixed.