From owner-freebsd-current Wed Nov 11 01:27:29 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id BAA24924 for freebsd-current-outgoing; Wed, 11 Nov 1998 01:27:29 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from morgan.angis.su.OZ.AU (morgan.angis.su.OZ.AU [129.78.25.38]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id BAA24902 for ; Wed, 11 Nov 1998 01:27:24 -0800 (PST) (envelope-from tonym@angis.usyd.edu.au) Received: (from tonym@localhost) by morgan.angis.su.OZ.AU (8.8.7/8.6.6) id UAA29192; Wed, 11 Nov 1998 20:26:28 +1100 (EST) Date: Wed, 11 Nov 1998 20:26:28 +1100 (EST) From: Tony Maher Message-Id: <199811110926.UAA29192@morgan.angis.su.OZ.AU> To: andreas@klemm.gtn.com Subject: Re: Travan TR4 dump/restore Cc: current@FreeBSD.ORG Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > my personal experience was, that it's now safe with CAM to use > blocksizes over 32 .... Since physio (if I remember right) was > done in 32 blocks chunks even is you choose 64 or more ... Justed dumped whole system again this time using 32 instead of 64. dump 0uabf 32 /dev/nrsa0 / dump 0uabf 32 /dev/nrsa0 /usr dump 0uabf 32 /dev/nrsa0 /var dump 0uabf 32 /dev/nrsa0 /n/01 dump 0uabf 32 /dev/nrsa0 /n/02 mt -f /dev/nrsa0 fsf 2 restore ivf /dev/nrsa0 and extracted subdirectory perfectly. It definitely didnt like 64 blocks last nite. Maybe something about this particular drive?! sa0: Removable Sequential Access SCSI2 device Well as long as it backups up the files ;-) I'll put the old drive back on later tonite if I get the chance and try it again with 32 blocks. Reading sa (4) man page The block size used may be any value supported by the device, the SCSI adapter and the system (usually between 1 byte and 64 Kbytes, sometimes more). Pretty sure the old drive under 2.2.-stable supported 64 (hard to test now). thanks again. tonym . To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message