From owner-freebsd-current Fri Dec 17 8:48:47 1999 Delivered-To: freebsd-current@freebsd.org Received: from gndrsh.dnsmgr.net (GndRsh.dnsmgr.net [198.145.92.4]) by hub.freebsd.org (Postfix) with ESMTP id 3F82115703 for ; Fri, 17 Dec 1999 08:48:44 -0800 (PST) (envelope-from freebsd@gndrsh.dnsmgr.net) Received: (from freebsd@localhost) by gndrsh.dnsmgr.net (8.9.3/8.9.3) id IAA29595; Fri, 17 Dec 1999 08:48:30 -0800 (PST) (envelope-from freebsd) From: "Rodney W. Grimes" Message-Id: <199912171648.IAA29595@gndrsh.dnsmgr.net> Subject: Re: Weird story with dump | restore In-Reply-To: <19991217123742.A70473@myhakas.matti.ee> from Vallo Kallaste at "Dec 17, 1999 12:37:42 pm" To: vallo@solaris.matti.ee Date: Fri, 17 Dec 1999 08:48:30 -0800 (PST) Cc: freebsd-current@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL54 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > On Fri, Dec 17, 1999 at 10:47:59AM +0200, Vallo Kallaste wrote: > > [snip] > > > It's very annoying, I have only fair experiences with dump/restore back > > to the 2.2.2 days until now. > > Sorry for the long post and partially? false alert. > > Something in my mind waked up and I checked what type of bsize and fsize > the other machines have. Now I remember a little discussion in the > cvs-all list, at that time phk committed something about default flags > for newfs or so and there was rgrimes involved into discussion. He was > suggesting following flags for filesystem creation for newer, bigger > disks: > > newfs -b16384 -f2048 -u2048 -c128 -i4096 > > I've used them since with no problems whatsoever. Now I got the dump > done on the machine with default filesystem, the bugger is unusual > filesystem I guess. Is it expected behavior? Does anybody know why it > can't be done? A few more details please. Are you having problems when you are dumping from a file system formatted as above, or is it a restore going to this type of file system, or are both the source and destination file system formatted as above? EXACTLY what dump/restore pipeline command did you run? I'll try to duplicate this here... I suspect a blocking/unblocking operation is highly un optimized to deal with these large block size file systems and/or your exasting a kernel resource during this operation. -- Rod Grimes - KD7CAX @ CN85sl - (RWG25) rgrimes@gndrsh.dnsmgr.net To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message