Bug 14121
| Summary: | resurfaced bug in rmt preventing remote dumps | ||
|---|---|---|---|
| Product: | Base System | Reporter: | ddr <ddr> |
| Component: | misc | Assignee: | freebsd-bugs (Nobody) <bugs> |
| Status: | Closed FIXED | ||
| Severity: | Affects Only Me | ||
| Priority: | Normal | ||
| Version: | 3.3-RELEASE | ||
| Hardware: | Any | ||
| OS: | Any | ||
State Changed From-To: open->feedback Does this problem still occur in newer versions of FreeBSD, such as 4.3-RELEASE? State Changed From-To: feedback->closed 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. |
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: > Fix: Find the previous problem ticket for more information.. I can not locate it in GNATS. How-To-Repeat: Backing up a BSDI 2.1 machine to FreeBSD 3.3-RELEASE via rdump.