Skip site navigation (1)Skip section navigation (2)
Date:      Fri, 5 Jul 2002 10:13:59 -0700
From:      "David O'Brien" <obrien@FreeBSD.ORG>
To:        "Georg-W. Koltermann" <Georg.Koltermann@mscsoftware.com>
Cc:        current@FreeBSD.ORG
Subject:   Re: dump(8) is hosed
Message-ID:  <20020705101359.A89839@dragon.nuxi.com>
In-Reply-To: <1025887736.773.116.camel@hunter.muc.macsch.com>; from Georg.Koltermann@mscsoftware.com on Fri, Jul 05, 2002 at 06:48:56PM %2B0200
References:  <20020703083114.A7216@dragon.nuxi.com> <1025887736.773.116.camel@hunter.muc.macsch.com>

next in thread | previous in thread | raw e-mail | index | archive | help
On Fri, Jul 05, 2002 at 06:48:56PM +0200, Georg-W. Koltermann wrote:
> Am Mi, 2002-07-03 um 17.31 schrieb David O'Brien:
> > On a 27-June-2002 23:02:00 UTC system (just before ipfw2 went in,
> > pre-KSE3), dump will not complete dumping more than 5GB.  At that point
> > it stops responding properly to ^T, which should give "DUMP: 47.52% done,
> > finished in 1:19".  At the 5GB mark, ^T gives:
> > 
> >     load: 0.00  cmd: dump 3981 [physstr] 2.11u 43.06s 0% 1536k
> > 
> > and never changes.  The user and system times never advance.  Anybody
> > have any ideas?
> 
> For me it is broken in a different way. For a small FS like / it works,
> but dumping my /home, which is 4G, I get 
> 
>      DUMP: read error from /dev/ad0s5e: Invalid argument: [sector -1054739789]: count=-1
>      DUMP: read error from /dev/ad0s5e: Invalid argument: [sector -1054739788]: count=-1
>      DUMP: read error from /dev/ad0s5e: Invalid argument: [sector -1054739787]: count=-1
>      DUMP: read error from /dev/ad0s5e: Invalid argument: [sector -1054739786]: count=-1
>     
> and on and on. 

Simular to what I get (now that I looked in /var/log/messages):
kernel: ccd1: error 22 on component 2 block -431037296 (ccd block 7744633266)
kernel: ccd1: error 22 on component 1 block -431037168 (ccd block 7744633266)
kernel: ccd1: error 22 on component 2 block -431037168 (ccd block 7744633266)

 
> Maybe a 32 bit <--> 64 bit mismatch caused by UFS2?  My -current is of
> date=2002.06.27.22.00.00.

Maybe.  I'll forward this to someone that might know.

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?20020705101359.A89839>