![]() |
|
|
|
|
|||||||
| Forums | Portal | Register | Forum Rules | FAQ | Contribute | Members List | Arcade | Search | Today's Posts | Mark Forums Read |
| UNIX for Dummies Questions & Answers If you're not sure where to post a UNIX or Linux question, post it here. All UNIX and Linux newbies welcome !! |
|
|
Submit Tools | LinkBack | Thread Tools | Search this Thread | Display Modes |
|
#1
|
||||
|
||||
|
/dev/rmt/0cn
Following the below info:
---------------------------------------------------------------------------------- # SYNTAX: /dev/rmt/<unit number><density>[<BSD behavior>][<no rewind>] · Density: l, m, h, u/c (low, medium, high, ultra/compressed, respectively) · BSD behavior: (optional) b · no rewind: (optional) n · For example, /dev/rmt/0hbn specifies unit 0, high density, BSD behavior and no rewind. ---------------------------------------------------------------------------------- I do: <pre> mt -f /dev/rmt/0cn rewind ufsdump 0uf /dev/rmt/0cn /dev/dsk/c0t0d0s0 </pre> When I restore I use: <pre> ufsrestore i (interactive) without define the "/dev/rmt/0cn". By default the ufsrestore is using "/dev/rmt/0" but I still get the restore correct. What is the use of the /dev/rmt/0cn ?? Thanks for your help !! |
| Forum Sponsor | ||
|
|
|
#2
|
||||
|
||||
|
Most tape drivers these days will ignore your request to set the drive to the wrong density when reading. Instead, they sense the tape's density and will silently change the density to whatever is correct. But if you work on an old 9-track tape drive you may find that the driver has no easy way to sense density and the tape will seem to be unreadable.
Many people will dump several filesystems on the same tape by specifying the no rewind bit. After the first dump, the tape is left positioned ready to write a second dump. If you wanted to restore a file from that second dump, you would first need to "mt fsf" to get there. You better specify the no rewind when you do. Then for the restore, you could use an auto-rewind special file. I almost always will use the no-rewind option. I can always do an explicit rewind when I want. |
|
#3
|
||||
|
||||
|
Quote:
What do you mean by that ?? Quote:
|
|
#4
|
|||
|
|||
|
HELP ME!!!
when i try fixing the s*.fx codex file it tells me " command line not accessable" and when i think ive fixed it its says" MISC.*.££" what does it all mean??
please help!!!
__________________
BY Severd_Nerv |
|
#5
|
||||
|
||||
|
Severd_Nerv,
This is TOTALLY irrelevant with the current thread, sorry. The thread is: quote: -------------------------------------------------------------------------------- . If you wanted to restore a file from that second dump, you would first need to "mt fsf" to get there. -------------------------------------------------------------------------------- I "ufsdump" many file systems as you said one after the other using the no rewind optionbut when I do a restore I use 'ufsrestore si (Number)' and restore the appropriate file system. What do you mean by that ?? quote: -------------------------------------------------------------------------------- . You better specify the no rewind when you do. Then for the restore, you could use an auto-rewind special file. -------------------------------------------------------------------------------- Thanks for your help |
|
#6
|
||||
|
||||
|
guest100, hmmm, I see you're right. That ability to specify a dump number doesn't exist on HP-UX and I never noticed it on Solaris. On both OS's I do restores the way I said, I fsf first to the proper file then do the restore.
Severd_Nerd, I don't understand at all what you are talking about. |
||||
| Google The UNIX and Linux Forums |