Date: Fri, 7 Jun 2002 13:30:37 -0700 From: "David O'Brien" <obrien@FreeBSD.ORG> To: Brooks Davis <brooks@one-eyed-alien.net> Cc: Bruce Evans <bde@zeta.org.au>, current@FreeBSD.ORG, phk@FreeBSD.ORG Subject: Re: dump (via amanda) causing panics Message-ID: <20020607133037.A59446@dragon.nuxi.com> In-Reply-To: <20020607125955.A29575@Odin.AC.HMC.Edu>; from brooks@one-eyed-alien.net on Fri, Jun 07, 2002 at 12:59:55PM -0700 References: <20020605222202.A17619@Odin.AC.HMC.Edu> <20020606155619.U10544-100000@gamplex.bde.org> <20020607125955.A29575@Odin.AC.HMC.Edu>
next in thread | previous in thread | raw e-mail | index | archive | help
On Fri, Jun 07, 2002 at 12:59:55PM -0700, Brooks Davis wrote: > On Thu, Jun 06, 2002 at 04:06:40PM +1000, Bruce Evans wrote: > > > This fixes the panic. It appears there's also another bug in dump > > > though. When I run dump I get this: ... > > > DUMP: master/slave protocol botched. > > > DUMP: The ENTIRE dump is aborted. ... > > 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. > > Applying phk's patch seems to have fixed it. It's a bit overkill for > fixing dump, but it did work and I guess this way I can do some limited > testing of the ufs2 patch. Can you reduce PHK's ufs2 patch down to the minium required to fix dump? That could then be committed now. 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?20020607133037.A59446>