From owner-freebsd-stable Sat Aug 28 20:29:25 1999 Delivered-To: freebsd-stable@freebsd.org Received: from binnacle.wantabe.com (binnacle.wantabe.com [209.16.8.14]) by hub.freebsd.org (Postfix) with ESMTP id 728D6150C5 for ; Sat, 28 Aug 1999 20:29:21 -0700 (PDT) (envelope-from jeffrl@wantabe.com) Received: from localhost (jeffrl@localhost) by binnacle.wantabe.com (8.9.2/8.9.2) with ESMTP id WAA50762 for ; Sat, 28 Aug 1999 22:28:44 -0500 (CDT) (envelope-from jeffrl@wantabe.com) X-Authentication-Warning: binnacle.wantabe.com: jeffrl owned process doing -bs Date: Sat, 28 Aug 1999 22:28:44 -0500 (CDT) From: "Jeffrey J. Libman" To: freebsd-stable@FreeBSD.ORG Subject: re: dump to remote system aborting Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG hi. i am running 3.1-release on a system, and just cvsup'd to bring it to 3.2-stable. before running the build world, i am attempting to back up to tape on a remote (old bsdi) system using dump. the first 3 file systems back up just fine, but the last, /dev/wd0s1f (/usr), aborts with the following: DUMP: dumping (Pass IV) [regular files] DUMP: master/slave protocol botched. DUMP: The ENTIRE dump is aborted. on examining the process list, there are still 5 dump processes running: 50676 p1 IN 0:00.92 /sbin/dump 0uBbf 2097152 1000 sail:/dev/nrst0 /dev/wd0s1f 50677 p1 IN 0:01.48 /sbin/dump 0uBbf 2097152 1000 sail:/dev/nrst0 /dev/wd0s1f 50678 p1 Z 0:00.00 (dump) 50679 p1 Z 0:00.00 (dump) 50680 p1 Z 0:00.00 (dump) can anybody tell me what master/slave protocol would be botched and how to get around or fix it? thanks in advance. cheers, jeff | |\ +------------------------------+ Jeffrey J. Libman, ops. mgr. | \ | Wantabe Internet Services | Wantabe, Inc. |__\ +------------------------------+ jeffrl@wantabe.com <-----|------> | access web cgi ftp news mail | (281) 493-0718 __,.-=\'`^`'~=-../__,.-= +------------------------------+ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message