Addendum to 6562 add note to man pages that refquota must be ignored during receive operations
In a recent discussion on illumos-discuss it became visible, that refquota is not receivable via zfs send/receive. It would be nice to have a note added to the docs about that at least so people are aware that this property must be excluded from replication for it to succeed.
Test case scenario
Refquota starts of as 1M
# zfs snap rpool1/testing@2 # zfs send -p -I @1 rpool1/testing@2 | zfs recv -F rpool1/testing2 # zfs set refquota=2M rpool1/testing # dd if=/dev/random of=/rpool1/testing/data.random bs=1m count=2 # zfs send -p -I @2 rpool1/testing@3 | zfs recv -F rpool1/testing2 cannot send rpool1/testing@3: snapshot rpool1/testing@3 does not exist cannot receive: failed to read from stream # zfs snap rpool1/testing@3 # zfs send -p -I @2 rpool1/testing@3 | zfs recv -F rpool1/testing2 cannot receive refquota property on rpool1/testing2: size is less than current used or reserved space # # zfs get refquota rpool1/testing2 NAME PROPERTY VALUE SOURCE rpool1/testing2 refquota 1M received # zfs get refquota rpool1/testing NAME PROPERTY VALUE SOURCE rpool1/testing refquota 2M local # ls -alh /rpool1/testing2/data.random -rw-r--r-- 1 root root 1.88M Apr 26 18:56 /rpool1/testing2/data.random # ls -alh /rpool1/testing/data.random -rw-r--r-- 1 root root 1.88M Apr 26 18:56 /rpool1/testing/data.random
Updated by Till Wegmüller about 2 years ago
Note: While I personally was not able to ignore refquota somehow the user that reported the issue was able to use -x to exclude the property from sync.