Skip site navigation (1)Skip section navigation (2)
Date:      Fri, 7 Jun 2002 15:07:16 -0700
From:      Brooks Davis <brooks@one-eyed-alien.net>
To:        Brooks Davis <brooks@one-eyed-alien.net>
Cc:        "David O'Brien" <obrien@FreeBSD.org>, Bruce Evans <bde@zeta.org.au>, current@FreeBSD.org, phk@FreeBSD.org
Subject:   Re: dump (via amanda) causing panics
Message-ID:  <20020607150716.A19826@Odin.AC.HMC.Edu>
In-Reply-To: <20020607141645.A8774@Odin.AC.HMC.Edu>; from brooks@one-eyed-alien.net on Fri, Jun 07, 2002 at 02:16:45PM -0700
References:  <20020605222202.A17619@Odin.AC.HMC.Edu> <20020606155619.U10544-100000@gamplex.bde.org> <20020607125955.A29575@Odin.AC.HMC.Edu> <20020607133037.A59446@dragon.nuxi.com> <20020607141645.A8774@Odin.AC.HMC.Edu>

index | next in thread | previous in thread | raw e-mail

[-- Attachment #1 --]
On Fri, Jun 07, 2002 at 02:16:45PM -0700, Brooks Davis wrote:
> On Fri, Jun 07, 2002 at 01:30:37PM -0700, David O'Brien wrote:
> > 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.
> 
> The changes to dump are rather large so I doubt I'd have much luck.
> Also, it appears I spoke too soon.  I was able to dump / and /var, but
> my /usr partition failed when I did another amanda run.  I'm running a
> new test to /dev/null to see if I get anything useful out of it.

Here's a sample of the errors I'm seeing:

  DUMP: read error from /dev/ad0s2f: Invalid argument: [sector -1980991191]: count=-1
  DUMP: read error from /dev/ad0s2f: Invalid argument: [sector -1980991190]: count=-1
  DUMP: read error from /dev/ad0s2f: Invalid argument: [sector -1980991189]: count=-1
  DUMP: read error from /dev/ad0s2f: Invalid argument: [sector -1980991188]: count=-1
  DUMP: read error from /dev/ad0s2f: Invalid argument: [sector -1980991187]: count=-1
  DUMP: read error from /dev/ad0s2f: Invalid argument: [block 68174084]: count=-1
  DUMP: read error from /dev/ad0s2f: Invalid argument: [sector 68174084]: count=-1
  DUMP: read error from /dev/ad0s2f: Invalid argument: [sector 68174085]: count=-1
  DUMP: read error from /dev/ad0s2f: Invalid argument: [sector 68174086]: count=-1
  DUMP: read error from /dev/ad0s2f: Invalid argument: [sector 68174087]: count=-1
  DUMP: read error from /dev/ad0s2f: Invalid argument: [block 68174088]: count=-1
  DUMP: More than 32 block read errors from 135053456
  DUMP: This is an unrecoverable error.
  DUMP: Do you want to attempt to continue?: ("yes" or "no")

-- Brooks

-- 
Any statement of the form "X is the one, true Y" is FALSE.
PGP fingerprint 655D 519C 26A7 82E7 2529  9BF0 5D8E 8BE9 F238 1AD4

[-- Attachment #2 --]
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.0.6 (GNU/Linux)
Comment: For info see http://www.gnupg.org

iD8DBQE9AS6TXY6L6fI4GtQRAnv2AJ9YvXLLPLYZMfaaUY+u1S9rIT5E6gCgw2x+
Q0EUCvOxQtf05jrhJ16Nqkk=
=n3V+
-----END PGP SIGNATURE-----
help

Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20020607150716.A19826>