Here's an old call to ufsdump. Which numbers, etc for gtar to tape?
- From: dkcombs@xxxxxxxxx (David Combs)
- Date: 20 Aug 2012 21:20:23 -0400
Here's a ufsdump I used when I had ufs, not zfs:
/usr/sbin/ufsdump 0ucnbdsf 126 54000 13000 /dev/rmt/0cn /dev/rdsk/''$slice
Suppose I now want to gtar a big file foo.tar onto an empty tape;
what gtar command would I give, ie where if anywhere do those
numbers fit in?
I especially need to know what I use for the tape drive name.
(By the way, I currently have a VXA-2)
And, do I use a "c", as in cvf?
And that f there: that's the name of the file I'd
be *creating*, if I used "c".
But I'm not creating a file; I'm writing (appending)
to a tape.
Would I give a command like this?:
gtar [???]vf <name of tape drive, no rewind> <name of file to
be written/appended to the tape> > tarjob1.log
Now, suppose I have three (.tar) files, and I'd like to put
all three onto the mag-tape.
So, after the first one, I sure want NO rewind to happen.
Ditto for after the second one.
So, it will be three gtar commands, one after the other:
gtar cvf -- no, that's not correct, I'm not creating
a new mag tape?
Anyway, in whatever command to write to the tape, what's that
"f" going to be?
And I suppose the final arg will be the name of the .tar-file
I want to write onto the tape.
QUESTION: is there any different result (on the tape) between
gtar .... file1.tar file2.tar file3.tar
and three separate commands?:
gtar ... file1.tar
gtar ... file2.tar
gtar ... file3.tar
-------------------------------------------- READING THE TAPE:
I suppose each of those on-tape files is called, in the mt doc,
a "record". A "file"? or what?
Hmmm. I just looked -- some commands use "file", others
use "record". Please, what's the difference?
Now, suppose I mount the tape I want to read, and I want to
read the THIRD of those .tar-files.
I do this, correct?: mt fsf 2 ...
or is it: mt fsr 2 ...
(What diff between the two?)
Here's my own (old) notes on mt:
erase <<===== BWR!!! ERASES **ENTIRE TAPE** <<===
BWR: eof, weof: BWR: these cmds WRITE <count> EOF-marks "RIGHT HERE".
fsf <count>: Forward Space over count "FILES" (actually, over EOF-MARKS), to
be positioned READY TO READ the count+1th "file".
(It will then be positioned on the first block of the "file").
fsr: Forward space <n> RECORDS.
bsf <count>: BACKSPACE over <n> EOF marks, readyToRead that EOF'ed file.
(bsf: NOTE the "note" below)
(NOTE: if status SAYS you're at file 17, but you WANT number 15,
then do "bsf 3", ie "diff+1"!!! (amAt - Want + 1) (PLUS ONE!!)
Thanks much for for the answers to these vary basic questions.
(I ask you guys because I *really* can't afford to screw up!)
- Prev by Date: Re: LSI HBA och 3GB drives
- Next by Date: Re: My gtar run -- ended with "auto-logout". What's that, what's it mean?
- Previous by thread: Re: ZFS as SAN/NAS
- Next by thread: Re: Here's an old call to ufsdump. Which numbers, etc for gtar to tape?