From owner-freebsd-current Tue Jul 28 05:35:56 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id FAA03015 for freebsd-current-outgoing; Tue, 28 Jul 1998 05:35:56 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from Kitten.mcs.com (Kitten.mcs.com [192.160.127.90]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id FAA03010 for ; Tue, 28 Jul 1998 05:35:54 -0700 (PDT) (envelope-from karl@Mars.mcs.net) Received: from Mars.mcs.net (karl@Mars.mcs.net [192.160.127.85]) by Kitten.mcs.com (8.8.7/8.8.2) with ESMTP id HAA00430 for ; Tue, 28 Jul 1998 07:35:24 -0500 (CDT) Received: (from karl@localhost) by Mars.mcs.net (8.8.7/8.8.2) id HAA18439; Tue, 28 Jul 1998 07:35:24 -0500 (CDT) Message-ID: <19980728073523.02311@mcs.net> Date: Tue, 28 Jul 1998 07:35:23 -0500 From: Karl Denninger To: current@FreeBSD.ORG Subject: Serious Dump problems Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.84 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hi folks, I have an interesting one here... I have a dump tape which is intact, yet restore complains about "hole in map" and segv's when attempting to start up in interactive mode. It appears that dump and restore are VERY old, and nobody is maintaining them. Interestingly enough, a new dump of the same filesystem produces the same error, so I suspect a problem with dump where it is writing out a bad directory map. Any ideas on this one? Is there a more recent set of sources available somewhere that might not display this problem? Needless to say, unrestorable tapes are not my idea of a good time! -- -- Karl Denninger (karl@MCS.Net)| MCSNet - Serving Chicagoland and Wisconsin http://www.mcs.net/ | T1's from $600 monthly / All Lines K56Flex/DOV | NEW! Corporate ISDN Prices dropped by up to 50%! Voice: [+1 312 803-MCS1 x219]| EXCLUSIVE NEW FEATURE ON ALL PERSONAL ACCOUNTS Fax: [+1 312 803-4929] | *SPAMBLOCK* Technology now included at no cost To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message