9 More Discussions You Might Find Interesting
1. AIX
Hi
I need to make some restore tapes for our old AIX systems
I have purchased some DDS2 tapes and cleaning tapes
The tape drive is rmt0
what commands can I enter to run the cleaning tape through the drive
and are the any commands I can enter to test these drives
prior to using... (2 Replies)
Discussion started by: madmacher
2 Replies
2. AIX
Hi All,
Are there recommendations about the use of cleaning tapes in DDS devices?
Should I clean the tape only when the drive indicates cleaning? Should I clean it once a month, week, even every day?
Is it harmful to clean the tape every day?
Thanks for your insights.
--Peter (4 Replies)
Discussion started by: petervg
4 Replies
3. Solaris
hi,
i am using Solaris 8 on a sparc box and already have 4 tape drives in a backup libaray attached to my unix server. we have recently added 2 new tape drives to the libaray and now want to get unix to see them. have it working in windows.
how do i scan for new hardware and add theses new... (5 Replies)
Discussion started by: dshakey
5 Replies
4. Solaris
I have a server/domain on a m5000 running Solaris 10. It is part of a cluster.
The other cluster member sees tape drives, but this one does not.
It is zoned correctly, and I can see the drives are binded in lputil.
The st.conf, and devlink.tab are identical.
ST.CONF: -
#
# Copyright... (1 Reply)
Discussion started by: pfwhufc
1 Replies
5. UNIX for Dummies Questions & Answers
Hi all
I have BIG headache with an old unix server I have and I need some help and ideas how to solve them effectively. Thanks in advance
***Story***
I have an OLD SCO OpenServer 5 release 5 server with DDS4 tape device.
I also have a box full of DDS4 tapes with data inside. I... (3 Replies)
Discussion started by: khaos83_2000
3 Replies
6. UNIX for Dummies Questions & Answers
Dear Experts and Advanced User,
I encounter a rare problem as mentioned above. I am not able to read the tape cartridge using the following command:
#dd if=/dev/rmt/0mnb ibs=16k | tar tvf -
It will prompt me with the message saying DD I/O error, broken pipe; everytime the above command... (1 Reply)
Discussion started by: stufftiger
1 Replies
7. Solaris
Hello, I am trying to copy a boot tape DDS-01 with miniroot, but i donīt get this copy. i have already used the command dd, but donīt work. There are other way to get it. (0 Replies)
Discussion started by: carelias
0 Replies
8. UNIX for Dummies Questions & Answers
Hey guys,
I'm trying to mount a SUN DDS-2 tape drive on a SUN Ultra 80 machine running Solaris 9. I had the SCSI drive connected at time of install, I'm very new to Solaris so I don't know if Solaris would detect the drive like that and install some form of device driver. But, what im posting... (2 Replies)
Discussion started by: kingdbag
2 Replies
9. Shell Programming and Scripting
is it possible to see what is in a dds tape?
like in dos, we can write dir a: to see the contents of it?
thanks
PS : actually, i came from a DOS background. so most of the time, i will try to relate unix to dos. of course, dos never came close to unix. but unix is like many instances of dos... (3 Replies)
Discussion started by: yls177
3 Replies
FMS(8) AFS Command Reference FMS(8)
NAME
fms - Determine a tape's capacity and a tape device's filemark size
SYNOPSIS
fms -tape <tape special file> [-help]
fms -t <tape special file> [-h]
DESCRIPTION
The fms command determines the capacity of the tape currently in the tape device identified by the -tape argument, along with the size of
the filemark for the device. The filemark is also referred to as the device's end-of-file (EOF) marker, and can differ for each combination
of tape and tape device.
As the Tape Coordinator writes a dump, it writes a filemark between the data included from each volume and also tracks the amount of space
left before the end of the tape (EOT). For some tape devices, the filemark is large enough (multiple megabytes) that failure to consider it
leads the Tape Coordinator significantly to overestimate the available space.
The intended use of this command is to determine tape capacity and filemark size values that can be specified in a tape device's entry in
the /var/lib/openafs/backup/tapeconfig file. For certain types of tape drives, the Tape Coordinator operates more efficiently when the
tapeconfig file lists accurate values. For further discussion, see the OpenAFS Administration Guide chapter on configuring the Backup
System.
Insert a tape in the drive before issuing this command.
CAUTIONS
Do not use this command on compressing tape devices in compression mode or with tape devices that handle tapes of multigigabyte (or
multiterabyte) capacity. It does not produce accurate results in those cases. For alternate suggestions on the values to record in the
tapeconfig file for compressing drives, see the OpenAFS Administration Guide chapter on configuring the Backup System.
Running the command completely overwrites the tape, so use a blank one or one that can be recycled.
Because it writes filemarks to the complete length of the tape, the command can take from several hours to more than a day to complete.
OPTIONS
-tape <tape special file>
Specifies the UNIX device name of the tape device for which to determine filemark size and the capacity of the tape it currently
contains. The format varies on different system types, but usually begins with /dev; an example is /dev/sd0a.
-help
Prints the online help for this command. All other valid options are ignored.
OUTPUT
The command generates output both on the standard output stream and in the fms.log file that it creates in the current working directory.
The output reports the capacity of the tape in the device and the device's filemark size.
The first few lines of output include status information about the execution of the command, including such information as the number of
blocks and the number of file marks written to the tape by the command. The last two lines of both screen and file output provide the
following information:
o "Tape capacity is number bytes": specifies the size, in bytes, of the tape in the device.
o "File marks are number bytes": specifies the device's filemark size in bytes.
The following message indicates that the fms command interpreter cannot access the tape device. The command halts.
Can't open tape drive I<device>
The following message indicates that the command interpreter cannot create the fms.log log file. Again, the command halts.
Can't open log file
EXAMPLES
The following command illustrates the output for the device called /dev/rmt1h:
% fms /dev/rmt1h
wrote block: 130408
Finished data capacity test - rewinding
wrote 1109 blocks, 1109 file marks
Finished file mark test
Tape capacity is 2136604672 bytes
File marks are 1910205 bytes
The following appears in the fms.log file:
fms test started
wrote 9230 blocks
Finished file mark test
Tape capacity is 151224320 bytes
File marks are 2375680 bytes
PRIVILEGE REQUIRED
The issuer must be able to insert and write to files in the currently working directory, if the fms.log file does not already exist. If it
already exists, the issuer need only be able to write to it.
SEE ALSO
fms.log(5), tapeconfig(5)
COPYRIGHT
IBM Corporation 2000. <http://www.ibm.com/> All Rights Reserved.
This documentation is covered by the IBM Public License Version 1.0. It was converted from HTML to POD by software written by Chas
Williams and Russ Allbery, based on work by Alf Wachsmann and Elizabeth Cassell.
OpenAFS 2012-03-26 FMS(8)