Path: utzoo!utgpu!jarvis.csri.toronto.edu!mailrus!tut.cis.ohio-state.edu!ucbvax!decwrl!shelby!portia!forel!karish
From: karish@forel.stanford.edu (Chuck Karish)
Newsgroups: comp.unix.ultrix
Subject: Re: dump on old 1.2 Ultrix...
Message-ID: <4113@portia.Stanford.EDU>
Date: 31 Jul 89 21:51:44 GMT
References: <412@wuee1.wustl.edu> <4082@portia.Stanford.EDU> <7484@cbmvax.UUCP>
Sender: USENET News System <news@Portia.stanford.edu>
Reply-To: karish@forel.stanford.edu (Chuck Karish)
Organization: Mindcraft, Inc.
Lines: 32

In article <7484@cbmvax.UUCP> grr@cbmvax.UUCP (George Robbins) wrote:
>In article <4082@portia.Stanford.EDU> karish@forel.stanford.edu
(Chuck Karish) writes:
>> In article <412@wuee1.wustl.edu> tjs@wuee1.wustl.edu.UUCP
(tom sullivan) wrote:
>> >we're still running old Ultrix 1.2 on our uVAX-II/GPX.

>> >is there an optimal setting (density, lenght, blocking factor, etc.)
>> >to do dumps onto a TK50 drive.

>> As George Robbins points out, dump accepts the `-b' flag.  The maximum
>> value for this flag is 126, as in 126 blocks or 63K.  This works for
>> tar, too, and speeds up the TK50 a lot.

>Does -b 126 really work with TK50's?  I get the feeling you're generalizing
>from Suns, rather than DEC stuff.  My recollection is that -b 63 is the
>biggest that will work with traditional (massbus TU78) drives, and there
>are blocksize limitations described for the PMAX SCSI TK50 that would
>limit you to -b 32.


	A uVAX-II/GPX has neither a Massbus nor a SCSI bus, and
	`-b 126' works.  I used it for a tar backup to TK50 on a
	uVAX-II/GPX running 3.0, last week.  It's been a while since I
	used the flag on a 1.2 system, but it worked then, too.  I'm
	not absolutely sure that it worked on dump/restore, but I think
	it did.



	Chuck Karish		{decwrl,hpda}!mindcrf!karish
	(415) 493-9000		karish@forel.stanford.edu