Date: Thu, 6 Jun 2002 16:06:40 +1000 (EST) From: Bruce Evans <bde@zeta.org.au> To: Brooks Davis <brooks@one-eyed-alien.net> Cc: current@FreeBSD.ORG Subject: Re: dump (via amanda) causing panics Message-ID: <20020606155619.U10544-100000@gamplex.bde.org> In-Reply-To: <20020605222202.A17619@Odin.AC.HMC.Edu>
next in thread | previous in thread | raw e-mail | index | archive | help
On Wed, 5 Jun 2002, Brooks Davis wrote: > This fixes the panic. It appears there's also another bug in dump > though. When I run dump I get this: > > [10:15pm] brooks@minya (~): sudo dump -a -f /dev/null /var > Password: > DUMP: Date of this level 0 dump: Wed Jun 5 22:16:09 2002 > DUMP: Date of last level 0 dump: the epoch > DUMP: Dumping /dev/ad0s2e (/var) to /dev/null > DUMP: mapping (Pass I) [regular files] > DUMP: mapping (Pass II) [directories] > DUMP: estimated 580085 tape blocks. > DUMP: dumping (Pass III) [directories] > DUMP: dumping (Pass IV) [regular files] > DUMP: master/slave protocol botched. > DUMP: The ENTIRE dump is aborted. > > Any idea what this problem is? I guess this is another 64-bit daddr_t problem. At least `daddr_t idblk[MAXNINDIR]' in traverse.c seems to be broken. This seems to be fixed in the ufs2 patch. There as another report about this earlier today, in a PR IIRC. Bruce 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?20020606155619.U10544-100000>