From owner-freebsd-scsi Sat May 25 02:14:12 1996 Return-Path: owner-freebsd-scsi Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id CAA22501 for freebsd-scsi-outgoing; Sat, 25 May 1996 02:14:12 -0700 (PDT) Received: from news1.gtn.com (news1.gtn.com [192.109.159.3]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id CAA22478 for ; Sat, 25 May 1996 02:14:06 -0700 (PDT) Received: (from uucp@localhost) by news1.gtn.com (8.7.2/8.7.2) id LAA03380; Sat, 25 May 1996 11:00:27 +0200 (MET DST) Received: from localhost (localhost [127.0.0.1]) by knobel.gun.de (8.7.5/8.7.3) with SMTP id KAA01229; Sat, 25 May 1996 10:57:18 +0200 (MET DST) Date: Sat, 25 May 1996 10:57:17 +0200 (MET DST) From: Andreas Klemm To: Wilko Bulte cc: joerg_wunsch@uriah.heep.sax.de, freebsd-scsi@freebsd.org Subject: Re: dump and 32blocks limit In-Reply-To: <199605241729.TAA20959@yedi.iaf.nl> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-scsi@freebsd.org X-Loop: FreeBSD.org Precedence: bulk -----BEGIN PGP SIGNED MESSAGE----- On Fri, 24 May 1996, Wilko Bulte wrote: > > As Wilko Bulte wrote: > > > > > I'm not absolutely sure this is SCSI-only related but: > > > > > > I grabbed the -current dump sources and found a 32 block limit builtin > > > there. Comment sez: restore can't read >32, maybe a bug in the tapedriver. > > > > > > I was aware of 64kbyte rawio limit, but this 32 is new to me. I ran > > > dumps with 128 (== 64kbyte) and never had restore nuke me. > > > > The claim with the 32 KB blocking was Andreas Klemm's one. > > Andreas, > Any more info on this?? 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). But when I tried to read those tapes with restore, I got an error message (forgot which exactly), you could perhaps browse the -current list for my e-mail... The result was, that I was only able to restore dumps that were made with a blocksize <= 64 blocks if I remember exactly. Untli this bug is fixed somewhere in kernel land I had the idea to disallow blocksizes >64 blocks in dump ... I think people wouldn't find it funny, if they are unable to restore their backups in case they saved the time of verifying a dump ;-)) Don't ask me, what's exactly the reason for this ... Was this broken in 1.1.5.1, too ??? I don't know... Andreas /// - -- andreas@knobel.gun.de /\/\___ Wiechers & Partner Datentechnik GmbH Andreas Klemm ___/\/\/ $$ Support Unix - aklemm@wup.de $$ pgp p-key http://www-swiss.ai.mit.edu/~bal/pks-toplev.html >>> powered by <<< ftp://sunsite.unc.edu/pub/Linux/system/Printing/aps-491.tgz >>> FreeBSD <<< -----BEGIN PGP SIGNATURE----- Version: 2.6.2 iQCVAwUBMabLbfMLpmkD/U+FAQEt3wP+LAENrddACZZFvGOYSLlfGbYaXUZy0CtV OTdLNsJHU9DnqlFzTcQEtkGFD47nILUTHRCXfKYDQGaTIMXTObZTTGhdDHjGt57l +0D7owaomIlc1glT5VLGocIU0GgXHlfZUbL1PT+yfPu+iXh3DS7CL9sPE8YLLQAf 0/7d4WKfSs0= =GF4S -----END PGP SIGNATURE-----