cannot receive incremental stream: dataset is busy

All your general support questions for OpenZFS on OS X.

cannot receive incremental stream: dataset is busy

Postby MichaelNewbery » Sat Jun 20, 2020 9:59 pm

On Mojave, zfs version 1.9.4, but identical results on 1.9.3.1.
I'm trying to make a backup of a zvol before I try to resize it, (just in case). When I try to zfs recv, I consistently get the error:
cannot receive incremental stream: dataset is busy
I have tried both zfs send to a file and subsequent receive, and piping send and receive together.
I.e.
Code: Select all
# zfs send -vceLR Wells/TM/Camel@2020-06-20 > Wells/TM/Camel-backup; zfs receive -Fv Wells/TM/Camel-backup < Wells/TM/Camel-backup
and
Code: Select all
# zfs send -vceLR Wells/TM/Camel@2020-06-20 | zfs receive -Fv Wells/TM/Camel-backup
I managed to get ONE snapshot across, but then I get stuck doing the next.
Code: Select all
# zfs send -vceLR -I Wells/TM/Camel@2017-11-15 Wells/TM/Camel@2017-12-09 | zfs recv -Fv Wells/VMs/Camel-backup-2
skipping snapshot Wells/TM/Camel@2018-01-09 because it was created after the destination snapshot (2017-12-09)
... [ignored snapshots]
send from @2017-11-15 to Wells/TM/Camel@2017-12-09 estimated size is 1.27G
total estimated size is 1.27G
TIME        SENT   SNAPSHOT
receiving incremental stream of Wells/TM/Camel@2017-12-09 into Wells/VMs/Camel-backup-2@2017-12-09
17:28:43   62.7K   Wells/TM/Camel@2017-12-09
17:28:44   8.89M   Wells/TM/Camel@2017-12-09
17:28:45   40.9M   Wells/TM/Camel@2017-12-09
...
17:29:56   1.23G   Wells/TM/Camel@2017-12-09
17:29:57   1.23G   Wells/TM/Camel@2017-12-09
17:29:58   1.23G   Wells/TM/Camel@2017-12-09
17:29:59   1.24G   Wells/TM/Camel@2017-12-09
cannot receive incremental stream: dataset is busy


If I try to do a full receive I get
Code: Select all
#  zfs send -vceLR -I Wells/TM/Camel@2017-11-15 Wells/TM/Camel@2020-06-20 | zfs recv -Fv Wells/VMs/Camel-backup-2
skipping snapshot Wells/TM/Camel@2020-06-21 because it was created after the destination snapshot (2020-06-20)
send from @2017-11-15 to Wells/TM/Camel@2017-12-09 estimated size is 1.27G
send from @2017-12-09 to Wells/TM/Camel@2018-01-09 estimated size is 2.98G
...
send from @2020-06-19 to Wells/TM/Camel@2020-06-20 estimated size is 487M
total estimated size is 66.2G
TIME        SENT   SNAPSHOT
receiving incremental stream of Wells/TM/Camel@2017-12-09 into Wells/VMs/Camel-backup-2@2017-12-09
12:18:27   62.7K   Wells/TM/Camel@2017-12-09
12:18:28   62.7K   Wells/TM/Camel@2017-12-09
12:18:29   62.7K   Wells/TM/Camel@2017-12-09
12:18:30    700K   Wells/TM/Camel@2017-12-09
12:18:31   9.18M   Wells/TM/Camel@2017-12-09
12:18:32   16.0M   Wells/TM/Camel@2017-12-09
12:18:33   24.9M   Wells/TM/Camel@2017-12-09
...
12:21:04   1.22G   Wells/TM/Camel@2017-12-09
12:21:05   1.24G   Wells/TM/Camel@2017-12-09
12:21:06   1.25G   Wells/TM/Camel@2017-12-09
TIME        SENT   SNAPSHOT
12:21:08   62.7K   Wells/TM/Camel@2018-01-09
12:21:09   62.7K   Wells/TM/Camel@2018-01-09
12:21:10   62.7K   Wells/TM/Camel@2018-01-09
12:21:11   62.7K   Wells/TM/Camel@2018-01-09
12:21:12   62.7K   Wells/TM/Camel@2018-01-09
12:21:13   62.7K   Wells/TM/Camel@2018-01-09
12:21:14   62.7K   Wells/TM/Camel@2018-01-09
12:21:15   62.7K   Wells/TM/Camel@2018-01-09
12:21:16   62.7K   Wells/TM/Camel@2018-01-09
cannot receive incremental stream: dataset is busy
warning: cannot send 'Wells/TM/Camel@2018-01-09': signal received
TIME        SENT   SNAPSHOT
warning: cannot send 'Wells/TM/Camel@2018-02-02': Broken pipe
...
TIME        SENT   SNAPSHOT
warning: cannot send 'Wells/TM/Camel@2020-06-19': Broken pipe
User avatar
MichaelNewbery
 
Posts: 10
Joined: Sat May 31, 2014 7:38 pm
Location: New Zealand

Return to General Help

Who is online

Users browsing this forum: No registered users and 3 guests