Date: Sun, 26 May 1996 13:15:58 +0200 (MET DST) From: Wilko Bulte <wilko@yedi.iaf.nl> To: joerg_wunsch@uriah.heep.sax.de Cc: andreas@knobel.gun.de, freebsd-scsi@freebsd.org, davidg@freebsd.org, dyson@freebsd.org Subject: Re: dump and 32blocks limit Message-ID: <199605261115.NAA09113@yedi.iaf.nl> In-Reply-To: <199605252037.WAA27101@uriah.heep.sax.de> from "J Wunsch" at May 25, 96 10:37:47 pm
next in thread | previous in thread | raw e-mail | index | archive | help
As J Wunsch wrote... > As Andreas Klemm wrote: > > > Well, sometimes I had a SUN 4mm DAT (Archive Python) at home. > > When doing backups with dump everything seemed to be fine. I could > > choose blocksizes of about 96 blocks (as it's usual on Sun's). > > Ah! This raises a flag... you've been using 96 KB blocking. Sigh. > Now look at the 64 KB physio limitation: your 96 KB has been accepted > by dump(8), but physio(9) split it into one 64 KB block (due to its > limit), and one 32 KB block. This gives you a tape with alternate > 64/32/64/32 KB blocking, nothing you would really like to have... Ah (again ;-) This is of course in line with my observation of multiple drive types never being bothered by 64 Kbyte. > So we should bump the limit to 64 KB, and explain the limitation of > physio in the man page (until it's been fixed -- which should remain a > goal, think of importing tapes with > 64 KB blocking). Yep. Makes my DLT quicker also :) Wilko _ __________________________________________________________________________ | / o / / _ Wilko Bulte email: wilko@yedi.iaf.nl |/|/ / / /( (_) Private FreeBSD site - Arnhem - The Netherlands --------------------------------------------------------------------------------
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?199605261115.NAA09113>