There are multiple quota objects now since ZFS on linux wanted support for their model aswell. Be carefull which you have enabled. Refquota says it should not but I know quota does. Let me test if that is an issue in docs though. Would be a bad.
The other thing is very Nexenta specific You may want to open a ticket with them the Community mostly does their own storage servers. Your idea with the incremental send of that one child dataset will work for sure. Not sure about a replicated send from the parent I would say no. Hope this helps Greetings Till On 23.04.20 21:07, Oliver Weinmann via illumos-discuss wrote: > Hi Till, > > Thanks a lot for your good explanation. It is really confusing as in the > manual it states that refquota doesn’t take descendants or snaps into > account. I might play around with bookmarks later. For now I guess I can use: > > zfs receive -x refquota to exclude the property? > > > How about I have started to recursively replicate a dataset and it failed on > one of the child datasets due to the refquota issue. Can I somehow resume the > replication of the parent dataset or do I have to replicate the child dataset > first using incremental snapshots? > > Normally I only use the built in auto sync feature on our nexenta storage, > but this time I have to sync back the data Manually to the nexenta system. > > Cheers, > Oliver > > Von meinem iPhone gesendet > >> Am 23.04.2020 um 18:04 schrieb Till Wegmüller <[email protected]>: >> >> Hi Oliver >> >> This is a usage issue with the zfs commands. Every snapshot also counts >> towards the quota. You may want to switch up and use bookmarks instead >> of snapshots as send sources. If you are changing the Refquota on a >> regular basis you will need to update both ends or use zfs send -p to >> copy all properties as well before the snapshots on the source get too >> huge again so you cannot send them any more. Another approach is not to >> save the properties at all and have no quota on the backup servers. You >> will need another script or config management to reapply the quota in >> case of a full restore but that would stop you getting this error. >> >> Hope this helps you get your backup process more streamlined >> If you still need help let me know. >> >> Greetings >> Till >> >>> On 23.04.20 16:29, oliver.weinmann via illumos-discuss wrote: >>> Hi folks, >>> >>> I'm currently trying to zfs send/recv using netcat between omnios >>> (sender) and nexenta (receiver). I usually get this error: >>> >>> cannot receive incremental stream: destination >>> >>> The source datasets have a refquota applied. I googled for the error but >>> it seems that there is no fix available yet? >>> >>> Due to this i'm not able to complete the zfs send / recv. I always have >>> to adjust the refquota on src and dest in order to proceed. Which is >>> really annoying as there are huge amount of data that have to be copied. :( >>> >>> Best Regards, >>> Oliver >>> *illumos <https://illumos.topicbox.com/latest>* / illumos-discuss / see >>> discussions <https://illumos.topicbox.com/groups/discuss> + participants >>> <https://illumos.topicbox.com/groups/discuss/members> + delivery options >>> <https://illumos.topicbox.com/groups/discuss/subscription> Permalink >>> <https://illumos.topicbox.com/groups/discuss/Tf2a07b0ee742a206-M6353a2efec2ba914bde49531> >>> ------------------------------------------ illumos: illumos-discuss Permalink: https://illumos.topicbox.com/groups/discuss/Tf2a07b0ee742a206-Mb9b1c00bef883d383f32e350 Delivery options: https://illumos.topicbox.com/groups/discuss/subscription
