From owner-freebsd-bugs@freebsd.org Tue Aug 22 02:26:58 2017 Return-Path: Delivered-To: freebsd-bugs@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id C6F4EDE85B6 for ; Tue, 22 Aug 2017 02:26:58 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from kenobi.freebsd.org (kenobi.freebsd.org [IPv6:2001:1900:2254:206a::16:76]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id B558B6CB46 for ; Tue, 22 Aug 2017 02:26:58 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from bugs.freebsd.org ([127.0.1.118]) by kenobi.freebsd.org (8.15.2/8.15.2) with ESMTP id v7M2Qw2w058011 for ; Tue, 22 Aug 2017 02:26:58 GMT (envelope-from bugzilla-noreply@freebsd.org) From: bugzilla-noreply@freebsd.org To: freebsd-bugs@FreeBSD.org Subject: [Bug 221707] zfs receive dry run fails but backup works Date: Tue, 22 Aug 2017 02:26:58 +0000 X-Bugzilla-Reason: AssignedTo X-Bugzilla-Type: new X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: Base System X-Bugzilla-Component: kern X-Bugzilla-Version: 11.1-RELEASE X-Bugzilla-Keywords: X-Bugzilla-Severity: Affects Only Me X-Bugzilla-Who: courtney.hicks1@icloud.com X-Bugzilla-Status: New X-Bugzilla-Resolution: X-Bugzilla-Priority: --- X-Bugzilla-Assigned-To: freebsd-bugs@FreeBSD.org X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: bug_id short_desc product version rep_platform op_sys bug_status bug_severity priority component assigned_to reporter Message-ID: Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable X-Bugzilla-URL: https://bugs.freebsd.org/bugzilla/ Auto-Submitted: auto-generated MIME-Version: 1.0 X-BeenThere: freebsd-bugs@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: Bug reports List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 22 Aug 2017 02:26:58 -0000 https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D221707 Bug ID: 221707 Summary: zfs receive dry run fails but backup works Product: Base System Version: 11.1-RELEASE Hardware: amd64 OS: Any Status: New Severity: Affects Only Me Priority: --- Component: kern Assignee: freebsd-bugs@FreeBSD.org Reporter: courtney.hicks1@icloud.com On a FreeBSD 11.1 system, I created a zpool that contains all my jails that= are created and managed with py3-iocage (built from ports) 0.99.1. I have set u= p my system to have zfs snapshots of the pool created and then backed up to an external hard drive connected via USB using zfs send/receive. Here is my process: Create snapshot: zfs snapshot -r iocage@`date +"%Y-%m-%d_%H:%M:%S"` Initial backup: zfs send -R iocage@date1 | zfs receive -vF backups/iocage backups is the zpool on my external HDD, which is imported at an altroot Incremental backup: zfs send -R -i iocage@date1 iocage@date2 | zfs receive -vF backups/iocage The problem: Before I sent my initial backup to my external HDD I ran this command: zfs send -R iocage@date1 | zfs receive -vnF backups/iocage This, however, produced this error: root@homeServer:~ # zfs send -R iocage@2017-08-19 | zfs receive -vnF backups/iocage would receive full stream of iocage@2017-08-19 into backups/iocage@2017-08-= 19 would receive full stream of iocage/iocage@2017-08-19 into backups/iocage/iocage@2017-08-19 would receive full stream of iocage/iocage/download@2017-08-19 into backups/iocage/iocage/download@2017-08-19 would receive full stream of iocage/iocage/download/11.1-RELEASE@2017-08-19 into backups/iocage/iocage/download/11.1-RELEASE@2017-08-19 would receive full stream of iocage/iocage/download/10.3-RELEASE@2017-08-19 into backups/iocage/iocage/download/10.3-RELEASE@2017-08-19 would receive full stream of iocage/iocage/releases@2017-08-19 into backups/iocage/iocage/releases@2017-08-19 would receive full stream of iocage/iocage/releases/10.3-RELEASE@2017-08-19 into backups/iocage/iocage/releases/10.3-RELEASE@2017-08-19 would receive full stream of iocage/iocage/releases/10.3-RELEASE/root@2017-08-19 into backups/iocage/iocage/releases/10.3-RELEASE/root@2017-08-19 would receive full stream of iocage/iocage/releases/11.1-RELEASE@2017-08-19 into backups/iocage/iocage/releases/11.1-RELEASE@2017-08-19 would receive full stream of iocage/iocage/releases/11.1-RELEASE/root@nextc= loud into backups/iocage/iocage/releases/11.1-RELEASE/root@nextcloud cannot receive incremental stream: destination 'backups/iocage/iocage/releases/11.1-RELEASE/root' does not exist warning: cannot send 'iocage/iocage/releases/11.1-RELEASE/root@minecraft': signal received warning: cannot send 'iocage/iocage/releases/11.1-RELEASE/root@webServer': Broken pipe warning: cannot send 'iocage/iocage/releases/11.1-RELEASE/root@plexMedia': Broken pipe warning: cannot send 'iocage/iocage/releases/11.1-RELEASE/root@homeBackup': Broken pipe warning: cannot send 'iocage/iocage/releases/11.1-RELEASE/root@reverseProxy= ': Broken pipe warning: cannot send 'iocage/iocage/releases/11.1-RELEASE/root@2017-08-19': Broken pipe I saw that it was saying backups/iocage/iocage/releases/11.1-RELEASE/root didn't exist, so I created that path, with each directory being its own zfs dataset (like it is on host). Once I did that, I got a new error: zfs send -R iocage/iocage@2017-08-19 | zfs receive -vnF backups/iocage would receive full stream of iocage/iocage@2017-08-19 into backups/iocage@2017-08-19 would receive full stream of iocage/iocage/download@2017-08-19 into backups/iocage/download@2017-08-19 would receive full stream of iocage/iocage/download/11.1-RELEASE@2017-08-19 into backups/iocage/download/11.1-RELEASE@2017-08-19 would receive full stream of iocage/iocage/download/10.3-RELEASE@2017-08-19 into backups/iocage/download/10.3-RELEASE@2017-08-19 would receive full stream of iocage/iocage/releases@2017-08-19 into backups/iocage/releases@2017-08-19 would receive full stream of iocage/iocage/releases/10.3-RELEASE@2017-08-19 into backups/iocage/releases/10.3-RELEASE@2017-08-19 would receive full stream of iocage/iocage/releases/10.3-RELEASE/root@2017-08-19 into backups/iocage/releases/10.3-RELEASE/root@2017-08-19 would receive full stream of iocage/iocage/releases/11.1-RELEASE@2017-08-19 into backups/iocage/releases/11.1-RELEASE@2017-08-19 would receive full stream of iocage/iocage/releases/11.1-RELEASE/root@nextc= loud into backups/iocage/releases/11.1-RELEASE/root@nextcloud would receive incremental stream of iocage/iocage/releases/11.1-RELEASE/root@minecraft into backups/iocage/releases/11.1-RELEASE/root@minecraft would receive incremental stream of iocage/iocage/releases/11.1-RELEASE/root@webServer into backups/iocage/releases/11.1-RELEASE/root@webServer would receive incremental stream of iocage/iocage/releases/11.1-RELEASE/root@plexMedia into backups/iocage/releases/11.1-RELEASE/root@plexMedia would receive incremental stream of iocage/iocage/releases/11.1-RELEASE/root@homeBackup into backups/iocage/releases/11.1-RELEASE/root@homeBackup would receive incremental stream of iocage/iocage/releases/11.1-RELEASE/root@reverseProxy into backups/iocage/releases/11.1-RELEASE/root@reverseProxy would receive incremental stream of iocage/iocage/releases/11.1-RELEASE/root@2017-08-19 into backups/iocage/releases/11.1-RELEASE/root@2017-08-19 would receive full stream of iocage/iocage/templates@2017-08-19 into backups/iocage/templates@2017-08-19 would receive full stream of iocage/iocage/jails@2017-08-19 into backups/iocage/jails@2017-08-19 would receive full stream of iocage/iocage/jails/webServer@2017-08-19 into backups/iocage/jails/webServer@2017-08-19 cannot receive: local origin for clone backups/iocage/jails/webServer/root@2017-08-19 does not exist warning: cannot send 'iocage/iocage/jails/webServer/root@2017-08-19': signal received However, as I said, removing -n from my input, the error goes away and the send/receive is successful. --=20 You are receiving this mail because: You are the assignee for the bug.=