frazier@oahu.cs.ucla.edu (Greg Frazier) (06/20/91)
Hello -
Could somebody give me the appropriate parameters for
doing a dump to an exebyte tape (2 gbyte)? For the record,
what I just tried was
dump 0usdf 6000 54000 /dev/rst1 filesystem
as specified in the man page. Thanks for any help.
--
Greg Frazier frazier@CS.UCLA.EDU !{ucbvax,rutgers}!ucla-cs!frazierjanet@cs.uwa.oz.au (Janet Jackson) (06/20/91)
In <1991Jun19.222701.29689@cs.ucla.edu> frazier@oahu.cs.ucla.edu (Greg Frazier) writes: >Hello - > Could somebody give me the appropriate parameters for >doing a dump to an exebyte tape (2 gbyte)? For the record, >what I just tried was > dump 0usdf 6000 54000 /dev/rst1 filesystem >as specified in the man page. Thanks for any help. And what went wrong? I'm using the same parameters, except I'm using a blocksize of 126, and it seems to work fine. (Don't think I've ever reached the end of a tape yet, though :-{ ) (that's supposed to be a look of consternation) Janet Jackson (janet@cs.uwa.oz.AU) Department of Computer Science The University of Western Australia
karl@thuja.gsfc.nasa.gov (Karl Anderson) (06/20/91)
In article <1991Jun19.222701.29689@cs.ucla.edu>, frazier@oahu.cs.ucla.edu (Greg Frazier) writes: |> Could somebody give me the appropriate parameters for |> doing a dump to an exebyte tape (2 gbyte)? For the record, |> what I just tried was |> dump 0usdf 6000 54000 /dev/rst1 filesystem |> as specified in the man page. Thanks for any help. |> -- I use b 126 and s 14025. I don't specify d. Works like a champ, for both local and remote dumps on an all-Sun network. -- Karl A. Anderson | Internet: karl@forest.gsfc.nasa.gov NASA/GSFC code 923 (STX) | voice: (301) 286-3815 Greenbelt, MD 20771 | #include "std_disclaimer"
frazier@oahu.cs.ucla.edu (Greg Frazier) (06/20/91)
janet@cs.uwa.oz.au (Janet Jackson) writes: >In <1991Jun19.222701.29689@cs.ucla.edu> frazier@oahu.cs.ucla.edu (Greg Frazier) writes: >>Hello - >> Could somebody give me the appropriate parameters for >>doing a dump to an exebyte tape (2 gbyte)? For the record, >>what I just tried was >> dump 0usdf 6000 54000 /dev/rst1 filesystem >>as specified in the man page. Thanks for any help. >And what went wrong? >I'm using the same parameters, except I'm using a blocksize of 126, and it >seems to work fine. (Don't think I've ever reached the end of a tape yet, >though :-{ ) (that's supposed to be a look of consternation) For the curious, here is the context. I am writing a dump script, and was testing/debugging it. An error msg similar to this appeared on the console: error on /dev/rst1: bad length parameter Let me say now that I'm a novice at system hacking. I did a (mt -f /dev/rst1 fsf 1) to skip a 10 meg file at the front of the tape, and attempted to dump 2 file systems onto the tape. These should have come to much less than 1 gig, let alone 2.3 gigs. I was not planning on keeping track of the amnt of tape already used, but rather to guarentee that the file systems being dumped on a single tape together had a lower capacity than the tape. It has been suggested to me that rdump'ing w/out specifying a blocksize is bad news - I'll try that as my first correction. -- Greg Frazier frazier@CS.UCLA.EDU !{ucbvax,rutgers}!ucla-cs!frazier
karrer@bernina.ethz.ch (Andreas Karrer) (06/21/91)
karl@thuja.gsfc.nasa.gov (Karl Anderson) writes: >frazier@oahu.cs.ucla.edu (Greg Frazier) writes: >|> Could somebody give me the appropriate parameters for >|> doing a dump to an exebyte tape (2 gbyte)? For the record, >|> what I just tried was >|> dump 0usdf 6000 54000 /dev/rst1 filesystem >|> as specified in the man page. Thanks for any help. >|> -- >I use b 126 and s 14025. I don't specify d. Works like a champ, for >both local and remote dumps on an all-Sun network. It would work even better if you used "buffer" as in: dump 0f - /dev/rXXX | rsh exahost "buffer -s 126b > /dev/exabyte" "buffer is a program that forks itself into a reader and a writer process that communicate thru shared memory. It is written by Lee McLoughlin, Imperial College, London. If you can't find it enywhere else, it's in ural.ethz.ch:software/source/buffer.tar.Z. +----------- Andi Karrer, Communication Systems, ETH Zuerich, Switzerland karrer@bernina.ethz.ch - terible simplifieur
trant@empower.corp.sgi.com (Ken Trant) (06/26/91)
Well, for what it's worth. I use a density of 408215 ( Total - 10% for warm fuzzy feeling). My command line looks like this: dump 0udbf $dens 512 $tape /dev/filesystem dens=408215 tape=nrtape Hope this helps. In article <1991Jun20.084904@thuja.gsfc.nasa.gov>, karl@thuja.gsfc.nasa.gov (Karl Anderson) writes: |> In article <1991Jun19.222701.29689@cs.ucla.edu>, |> frazier@oahu.cs.ucla.edu (Greg Frazier) writes: |> |> |> Could somebody give me the appropriate parameters for |> |> doing a dump to an exebyte tape (2 gbyte)? For the record, |> |> what I just tried was |> |> dump 0usdf 6000 54000 /dev/rst1 filesystem |> |> as specified in the man page. Thanks for any help. |> |> -- |> |> I use b 126 and s 14025. I don't specify d. Works like a champ, for |> both local and remote dumps on an all-Sun network. |> -- |> Karl A. Anderson | Internet: karl@forest.gsfc.nasa.gov -- Ken Trant <trant@sgi.com> / Third Star to the right Information Services, / And straight on till Silicon Graphics, Inc / Morning
trant@empower.corp.sgi.com (Ken Trant) (06/26/91)
The parameter used (6000) is wrong. The way I read his command line is he wants a level 0 dump, write the successful completion to /etc/dumpdates, tape length of 6000 feet, density and dump device. The exebyte is 112 meters or 4409.44 inches, or 453572 bpi (2000Mbytes on American exabyte tapes). I use 408215 as a density (minus 10%) for saftey sake. Also remember to use the no rewind device for multiple volumes on 1 tape. Good luck In article <frazier.677435824@oahu>, frazier@oahu.cs.ucla.edu (Greg Frazier) writes: |> janet@cs.uwa.oz.au (Janet Jackson) writes: |> |> >In <1991Jun19.222701.29689@cs.ucla.edu> frazier@oahu.cs.ucla.edu (Greg Frazier) writes: |> |> >>Hello - |> >> Could somebody give me the appropriate parameters for |> >>doing a dump to an exebyte tape (2 gbyte)? For the record, |> >>what I just tried was |> >> dump 0usdf 6000 54000 /dev/rst1 filesystem |> >>as specified in the man page. Thanks for any help. |> |> >And what went wrong? |> |> >I'm using the same parameters, except I'm using a blocksize of 126, and it |> >seems to work fine. (Don't think I've ever reached the end of a tape yet, |> >though :-{ ) (that's supposed to be a look of consternation) |> |> For the curious, here is the context. I am writing a dump script, |> and was testing/debugging it. An error msg similar to this appeared |> on the console: |> |> error on /dev/rst1: bad length parameter |> |> Let me say now that I'm a novice at system hacking. I did |> a (mt -f /dev/rst1 fsf 1) to skip a 10 meg file at the front |> of the tape, and attempted to dump 2 file systems onto the tape. |> These should have come to much less than 1 gig, let alone 2.3 gigs. |> I was not planning on keeping track of the amnt of tape already |> used, but rather to guarentee that the file systems being dumped |> on a single tape together had a lower capacity than the tape. It |> has been suggested to me that rdump'ing w/out specifying a blocksize |> is bad news - I'll try that as my first correction. |> -- |> |> |> Greg Frazier frazier@CS.UCLA.EDU !{ucbvax,rutgers}!ucla-cs!frazier -- Ken Trant <trant@sgi.com> / Third Star to the right Information Services, / And straight on till Silicon Graphics, Inc / Morning