From nobody@FreeBSD.ORG Mon Oct  4 09:19:24 1999
Return-Path: <nobody@FreeBSD.ORG>
Received: by hub.freebsd.org (Postfix, from userid 32767)
	id 348D81529C; Mon,  4 Oct 1999 09:19:24 -0700 (PDT)
Message-Id: <19991004161924.348D81529C@hub.freebsd.org>
Date: Mon,  4 Oct 1999 09:19:24 -0700 (PDT)
From: ddr@gwis.com
Sender: nobody@FreeBSD.ORG
To: freebsd-gnats-submit@freebsd.org
Subject: resurfaced bug in rmt preventing remote dumps
X-Send-Pr-Version: www-1.0

>Number:         14121
>Category:       misc
>Synopsis:       resurfaced bug in rmt preventing remote dumps
>Confidential:   no
>Severity:       serious
>Priority:       medium
>Responsible:    freebsd-bugs
>State:          closed
>Quarter:        
>Keywords:       
>Date-Required:  
>Class:          sw-bug
>Submitter-Id:   current-users
>Arrival-Date:   Mon Oct  4 09:20:00 PDT 1999
>Closed-Date:    Thu Jan 17 08:12:05 PST 2002
>Last-Modified:  Thu Jan 17 08:38:16 PST 2002
>Originator:     Dan Roberts
>Release:        3.3-RELEASE
>Organization:
GWIS Internet Solutions
>Environment:
FreeBSD foster.gwis.com 3.3-RELEASE FreeBSD 3.3-RELEASE #1: Sat Sep 25 10:51:42 EDT 1999 droberts@foster.gwis.com:/usr/src/sys/compile/FOSTER  i386
>Description:
This email was sent to questions@ a short time ago:

==========BEGIN===========This one just to make you know that the problem for I asked a solution in my previous message has been solved by applying a patch to rshd. It was a small bug (7381) in the rshd.c version of 2.2.7-RELEASE (I'm running that version on my target server). If someone has the same problem: search the bugs mailing for 7381 and you'll find the simple patch.

>  I'm currently using NFS and tar to backup 3 FreeBSD servers on the DAT tape >drive of a fourth server. I'd like to switch to dump/rdump, but when I try to >issue a dump -f command, it stops after the connection and analysis of the >local filesystem with a "protocol to remote tape server botched (code "Broken >pipe")" error:
>
>How-To-Repeat:
Backing up a BSDI 2.1 machine to FreeBSD 3.3-RELEASE via rdump.
>Fix:
Find the previous problem ticket for more information.. I can not locate it in GNATS.

>Release-Note:
>Audit-Trail:
State-Changed-From-To: open->feedback 
State-Changed-By: mike 
State-Changed-When: Fri Jul 20 18:57:40 PDT 2001 
State-Changed-Why:  

Does this problem still occur in newer versions of FreeBSD, 
such as 4.3-RELEASE? 

http://www.FreeBSD.org/cgi/query-pr.cgi?pr=14121 
State-Changed-From-To: feedback->closed 
State-Changed-By: sheldonh 
State-Changed-When: Thu Jan 17 08:12:05 PST 2002 
State-Changed-Why:  
Automatic feedback timeout.  If additional feedback that warrants 
the re-opening of this PR is available but not included in the 
audit trail, please include the feedback in a reply to this message 
(preserving the Subject line) and ask that the PR be re-opened. 

http://www.freebsd.org/cgi/query-pr.cgi?pr=14121 
>Unformatted:
 >local# dump -f remote:/dev/rst0 /var
 >  DUMP: Connection to remote established.
 >  DUMP: Date of this level 0 dump: Mon Feb 22 14:56:06 1999
 >  DUMP: Date of last level 0 dump: the epoch
 >  DUMP: Dumping /dev/rda0s2f (/var) to /dev/rst0 on host remote
 >  DUMP: mapping (Pass I) [regular files]
 >  DUMP: mapping (Pass II) [directories]
 >  DUMP: estimated 13026 tape blocks on 0.33 tape(s).
 >  DUMP: Protocol to remote tape server botched (code "Broken pipe").
 >  DUMP: Lost connection to remote host.
 >
 >  The local machine is in the root's .rhosts file of the remote machine
 and >rshd isn't commented out in the remote's /etc/inetd.conf. Of course
 dump works >well locally.=============END==============
 
 I experienced this same problem, backing a BSDI 2.1 machine to the FreeBSD server when I was running 2.2.7.. it went away when I upgraded, but now that I've installed 3.3-RELEASE, the problem is back.  Could you please check to see if this was re-broken? 
 
