From owner-freebsd-current Tue Mar 31 10:33:33 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id KAA11942 for freebsd-current-outgoing; Tue, 31 Mar 1998 10:33:33 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from narnia.plutotech.com (narnia.plutotech.com [206.168.67.130]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id KAA11936 for ; Tue, 31 Mar 1998 10:33:27 -0800 (PST) (envelope-from gibbs@narnia.plutotech.com) Received: (from gibbs@localhost) by narnia.plutotech.com (8.8.8/8.7.3) id LAA05074; Tue, 31 Mar 1998 11:26:54 -0700 (MST) Date: Tue, 31 Mar 1998 11:26:54 -0700 (MST) From: "Justin T. Gibbs" Message-Id: <199803311826.LAA05074@narnia.plutotech.com> To: shimon@simon-shapiro.org cc: current@FreeBSD.ORG Subject: Re: CONTINUED problems: Restore/Dump broken? Newsgroups: pluto.freebsd.current In-Reply-To: User-Agent: tin/pre-1.4-971204 (UNIX) (FreeBSD/3.0-CURRENT (i386)) Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In article you wrote: > >> I have tested the tape drive in two other machines (NT & Linux) and it >> works >> fine. Yes, I have verified that the termination is correctly installed >> and >> working. >> >> At this point, it seems "dump" works, but "restore" does not work in >> 3.0-CURRENT and I have been unable to resolve or fix the problem. >> >> Does anyone have any clues or suggestions that they could make to resolve >> the tape drive problems I'm having? > > Yes. I posted a note about it. Restore is not broken, neither is dump, > nor your tape drive. > > Dump dumps in multiples of 1024 bytes. With 3.-0-current, the only > blocking factor that works is 512 bytes, which is very, very slow. > I have found no way to convince dump to go to that size (short of changing > the source). I don't seem to have this problem with dump and restore here. In testing out the "new" CAM tape driver, we've made several dumps and restores using blocksizes much larger than 512bytes. These were usually performed to either an Archive Python DDS-2 drive or an Exabyte Eliant drive. One thing that could be biting you though is that dump defaults to a 10k block size while restore will default to a 32k block size. I haven't analyzed the source enough to see if it will properly handle cases where the blocksize is smaller than the default. I always explicitly specify the blocksize. -- Justin To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message