When I run znapzend with noaction:
Can there be a problem that at first, subvol-165-disk-0 snapshot is created and then recursive snapshot fails, because it already exists?
Hi I'm having a problem with my zfs backups sending. There were many days that my scheduled plan didn't work, so I have a bunch of snapshots (about 4 days worth) that are not backed up. I've run the plan manually and here is the logs:
cannot receive incremental stream: dataset is busy
mbuffer: error: outputThread: error writing to <stdout> at offset 0x55120000: Broken pipe
mbuffer: warning: error during output to <stdout>: Broken pipe
warning: cannot send 'zroot/data/timemachine@10-07-2021-00:00:00': signal received
warning: cannot send 'zroot/data/timemachine@10-07-2021-06:00:00': Broken pipe
warning: cannot send 'zroot/data/timemachine@10-07-2021-12:00:00': Broken pipe
warning: cannot send 'zroot/data/timemachine@10-07-2021-18:00:00': Broken pipe
warning: cannot send 'zroot/data/timemachine@10-08-2021-00:00:00': Broken pipe
warning: cannot send 'zroot/data/timemachine@10-08-2021-06:00:00': Broken pipe
warning: cannot send 'zroot/data/timemachine@10-08-2021-12:00:00': Broken pipe
warning: cannot send 'zroot/data/timemachine@10-08-2021-18:00:00': Broken pipe
warning: cannot send 'zroot/data/timemachine@10-09-2021-00:00:00': Broken pipe
warning: cannot send 'zroot/data/timemachine@10-09-2021-06:00:00': Broken pipe
warning: cannot send 'zroot/data/timemachine@10-09-2021-12:00:00': Broken pipe
warning: cannot send 'zroot/data/timemachine@10-09-2021-18:00:00': Broken pipe
warning: cannot send 'zroot/data/timemachine@10-10-2021-00:00:00': Broken pipe
warning: cannot send 'zroot/data/timemachine@10-10-2021-06:00:00': Broken pipe
warning: cannot send 'zroot/data/timemachine@10-10-2021-10:28:46': Broken pipe
warning: cannot send 'zroot/data/timemachine@10-10-2021-10:30:23': Broken pipe
cannot send 'zroot/data/timemachine': I/O error
[2021-10-10 10:31:06.50500] [80725] [warn] ERROR: cannot send snapshots to tank/backups/zfs_backup/arch-TM on root@10.0.1.197
[2021-10-10 10:31:06.50525] [80725] [warn] ERROR: suspending cleanup source dataset zroot/data/timemachine because 1 send task(s) failed:
[2021-10-10 10:31:06.50638] [80725] [warn] +--> ERROR: cannot send snapshots to tank/backups/zfs_backup/arch-TM on root@10.0.1.197
[2021-10-10 10:31:06.50655] [80725] [info] done with backupset zroot/data/timemachine in 43 seconds
[2021-10-10 10:31:06.50837] [80689] [debug] send/receive worker for zroot/data/timemachine done (80725)
znapzend (PID=80689) is done.
It seems to break at this step:
'/usr/local/bin/mbuffer -q -s 256k -W 600 -m 200M|zfs recv -F tank/backups/zfs_backup/arch-TM'
cannot receive incremental stream: dataset is busy
Is this a problem with the mbuffer command or something else?
zfs allow
delegations on Linux OpenZFS? Seems there are issues receiving as a non-root user into datasets with (direct or inherited) zoned=on
as I mentioned in the PRs... did anyone by chance find a workaround other than disabling the attribute as soon as received (and probably inheriting/defining local
mountpoints on the backup server to override received
ones)?