From owner-freebsd-bugs@FreeBSD.ORG Wed Aug 27 11:50:03 2008 Return-Path: Delivered-To: freebsd-bugs@hub.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 822861065682 for ; Wed, 27 Aug 2008 11:50:03 +0000 (UTC) (envelope-from gnats@FreeBSD.org) Received: from freefall.freebsd.org (freefall.freebsd.org [IPv6:2001:4f8:fff6::28]) by mx1.freebsd.org (Postfix) with ESMTP id 6C7128FC15 for ; Wed, 27 Aug 2008 11:50:03 +0000 (UTC) (envelope-from gnats@FreeBSD.org) Received: from freefall.freebsd.org (gnats@localhost [127.0.0.1]) by freefall.freebsd.org (8.14.2/8.14.2) with ESMTP id m7RBo3ra023640 for ; Wed, 27 Aug 2008 11:50:03 GMT (envelope-from gnats@freefall.freebsd.org) Received: (from gnats@localhost) by freefall.freebsd.org (8.14.2/8.14.1/Submit) id m7RBo3eI023639; Wed, 27 Aug 2008 11:50:03 GMT (envelope-from gnats) Date: Wed, 27 Aug 2008 11:50:03 GMT Message-Id: <200808271150.m7RBo3eI023639@freefall.freebsd.org> To: freebsd-bugs@FreeBSD.org From: Jaakko Heinonen Cc: Subject: Re: misc/126882: dump(8) ok, but restore(8) via -P and SSH failes X-BeenThere: freebsd-bugs@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: Jaakko Heinonen List-Id: Bug reports List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 27 Aug 2008 11:50:03 -0000 The following reply was made to PR bin/126882; it has been noted by GNATS. From: Jaakko Heinonen To: Matthias Apitz Cc: bug-followup@FreeBSD.org Subject: Re: misc/126882: dump(8) ok, but restore(8) via -P and SSH failes Date: Wed, 27 Aug 2008 14:45:54 +0300 On 2008-08-27, Matthias Apitz wrote: > $ restore -xv -P "ssh guru@albatros 'gzip -dc dumpsRebelion/usr.dmp.gz'" ./home/guru/myThings/Espanol/diario2008 > > partial block read: 16128 should be 16384 > partial block read: 256 should be 16384 > partial block read: 16128 should be 16384 > unknown tape header type 6697331 > abort? [yn] AFAIK restore(8) -P switch has been broken since it's introduction (in r128175). Please see the PR bin/121502 and the patches submitted to it. Those patches should fix the problem you are seeing. -- Jaakko