Path: utzoo!utgpu!watserv1!watmath!att!rutgers!usc!elroy.jpl.nasa.gov!suned1!suned1.nswses.navy.mil!jht
From: jht@suned1.nswses.navy.mil (James H Tibbs)
Newsgroups: comp.unix.admin
Subject: Re: Dumping to an exabyte tape drive
Keywords: Exabyte dump args
Message-ID: <1990Sep1.143812@suned1.nswses.navy.mil>
Date: 1 Sep 90 21:38:12 GMT
References: <1990Aug29.143657.20588@siesoft.co.uk> <FPB.90Aug31172357@schlitz.ittc.wec.com>
Sender: efb@suned1.Nswses.Navy.MIL
Reply-To: jht@suned1.nswses.navy.mil (Jim Tibbs)
Organization: Dept. of the Navy (NSWSES)
Lines: 24


  I used these arguments for an Exabyte on a Sun3 running 4.0.3 with the
standard
Sun drivers being used;

     dump 0ubsdf 64 12000 43000 /dev/rst1 "file-system"

  With these args about 1.9GB will fit on a tape before "write errors"
are encountered. This 1.9GB figure matches what dump "thinks" it can
fit
on a tape with the given args. According to the vendor who sold our
unit,
the blocking, size, and density parameters originated from Sun.
  Is anyone else out there using an Exabyte with Sun drivers which can
recognize the end of the tape?
  The above parameters have proved reliable as I have rebuilt a number
of
trashed disks/file systems ( :-( ) backed up on Exabytes.
--
    Jim Tibbs, System Administrator; UNIX/VMS/Networking
    Dept. of the Navy (NSWSES), Port Hueneme CA. 93043, Code 4A05
    Work#: (805) 982-7185 (A/v 551), Home#:(805) 984-6529
    jht@suned1.nswses.navy.mil                     jht@suned1.UUCP
    Any statements / opinions made here are mine alone, not the Navy's.