From owner-freebsd-hackers Tue May 5 09:42:57 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id JAA17004 for freebsd-hackers-outgoing; Tue, 5 May 1998 09:42:57 -0700 (PDT) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from misery.sdf.com (misery.sdf.com [204.244.213.32]) by hub.freebsd.org (8.8.8/8.8.8) with SMTP id JAA16978 for ; Tue, 5 May 1998 09:42:46 -0700 (PDT) (envelope-from tom@sdf.com) Received: from tom by misery.sdf.com with smtp (Exim 1.82 #3) id 0yWkOB-0005kH-00; Tue, 5 May 1998 09:16:19 -0700 Date: Tue, 5 May 1998 09:16:19 -0700 (PDT) From: Tom To: Terry Lambert cc: beng@lcs.mit.edu, freebsd-hackers@FreeBSD.ORG Subject: Re: Network problem with 2.2.6-STABLE In-Reply-To: <199805050816.BAA19281@usr02.primenet.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Tue, 5 May 1998, Terry Lambert wrote: > > Perhaps, but dump/restore is broken for large filesystems. Perhaps one > > of the dump/restore advocates should fix it before a new user is swayed by > > the rhetoric into using dump/restore, only to watch restore core dump on > > large dumps. > > Be happy to. Where is you real bug report that details the problem, > instead of just stating that there is one? So far, all I have seen Posted Apr 16 to freebsd-stable. The only response that I received was from someone that said, "thats just like the PR that I sent a long time ago". Anyhow, basically any kind of restore operation (restore -t, or restore -r) results in an immediate "hole in map" response, with a "abort? [yn]" prompt, and then about three seconds later, a segmentation fault. Tom To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message