Date: Thu, 06 Jun 2002 16:24:35 -0700 From: Manfred Antar <null@pozo.com> To: obrien@FreeBSD.ORG Cc: current@FreeBSD.ORG Subject: Re: dump on current broken -- master/slave protocol botched Message-ID: <5.1.1.6.2.20020606162335.00acce60@pozo.com> In-Reply-To: <20020606093036.C59829@dragon.nuxi.com> References: <5.1.1.6.2.20020605195136.00a78d18@pozo.com> <5.1.1.6.2.20020605195136.00a78d18@pozo.com>
next in thread | previous in thread | raw e-mail | index | archive | help
At 09:30 AM 6/6/2002 -0700, David O'Brien wrote: >On Wed, Jun 05, 2002 at 08:01:54PM -0700, Manfred Antar wrote: >> I have been using the following command to dump for months with no problem: >> dump 0fua /dev/nsa0 /dev/da0s1a >> >> for the past few weeks I get this: >> (bin)504}dump 0fua /dev/nsa0 /dev/da0s1a >> DUMP: Date of this level 0 dump: Wed Jun 5 19:54:04 2002 >> DUMP: Date of last level 0 dump: the epoch >> DUMP: Dumping /dev/da0s1a (/) to /dev/nsa0 >> DUMP: mapping (Pass I) [regular files] >> DUMP: mapping (Pass II) [directories] >> DUMP: estimated 67590 tape blocks. >> DUMP: dumping (Pass III) [directories] >> DUMP: dumping (Pass IV) [regular files] >> DUMP: master/slave protocol botched. >> DUMP: The ENTIRE dump is aborted. > >I am seeing this also. :-( Is your world & kernel in sync. I must admit >my kernel is May 17 (been avoiding some suspicious problems in SMP >kernels); but world is Jun 3rd. Everything in sync and current. Dump from May 3rd works ================================== || null@pozo.com || || Ph. (415) 681-6235 || ================================== To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?5.1.1.6.2.20020606162335.00acce60>