Path: utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!rutgers!bpa!cbmvax!grr From: grr@cbmvax.commodore.com (George Robbins) Newsgroups: comp.unix.ultrix Subject: Re: Exabyte dump problems Message-ID: <13222@cbmvax.commodore.com> Date: 16 Jul 90 04:35:34 GMT References: <10544@batcomputer.tn.cornell.edu> Reply-To: grr@cbmvax (George Robbins) Organization: Commodore, West Chester, PA Lines: 25 In article <10544@batcomputer.tn.cornell.edu> rogerj@tcgould.tn.cornell.edu (Roger Jagoda) writes: > Folks, > > I have inherited a UNIX system (VAX/ULTRIX) with a SCSI Exabyte (OEM'd 3rd Party as usual) Tape unit. My question regards the parameters for the best "dump" > command use. For example, we're using now: > > dump usdf 4800 6666 /dev/nrmt1h > > ... Actually, couldn't we just put a > very large number for the lenght (like 100000)? That number is just > so the tape doesn't run off the reel during the dump, right? Well, our > dumps don't take up 2.2G so there's probably no danger of that. Yes, subject to the concern that you don't use such impressive numbers that internal computations overflow... I'd use something like sd 36000 6250, which comes to "10 - 3600 foot tapes @6250 bpi, each of which hold not quite 200 M-byte". Other people have their own favorite lucky numbers. Uh, none of this should have the least effect on whether or not the dumps are readable - I'd look elsewhere for that problem! -- George Robbins - now working for, uucp: {uunet|pyramid|rutgers}!cbmvax!grr but no way officially representing: domain: grr@cbmvax.commodore.com Commodore, Engineering Department phone: 215-431-9349 (only by moonlite)