11-24-2009
Many thanks for the complete and fast reply!
This production system has not been available for me to reboot and view post messages. Would the post messages also be logged in /usr/adm/messages ? (I forgot to look there)
---------- Post updated at 06:18 PM ---------- Previous update was at 06:14 PM ----------
I was prepared to carry out the mkdev tape operation, but was not able to since I could not reboot the production system. But I have a question about the procedure I found as (shown below): does mkdev tape perform the re-link since it rebuilds the kernel?
# mkdev tape
Pick 1) Install a Tape Drive
Pick 4) Install SCSI Tape Drive
Pick Yes Do you wish to configure the SCSI Tape Drive now? (y/n?)
Pick 0-7 What is the ID of the controller for this device?
Pick 0 or 1 Which SCSI host adapter supports this device?
Pick 0 What is the LUN of this device? Always enter 0 for the LUN.
You will then see:
The following special devices have been created:
/dev/rStp# /dev/nrStp# /dev/xStp#
Press <Return> to Continue.
The original Tape Drive Configuration Program menu will then be displayed.
Press "q" to quit and you will be asked:
You must create a new kernel to affect the driver change you specified.
Do you wish to create a new kernel now? (y/n)
Choose "y" and you will see the message:
The UNIX Operating System will now be rebuilt.
This is take a few minutes. Please wait.
Root for this system build it /.
This will take a few minutes and then you will be asked:
Do you want this kernel to boot by default? (y/n)
Again, answer "y".
Next you will be asked:
Do you want the kernel environment rebuilt? (y/n)
Again, answer "y".
When you receive a root prompt, shut the system down and reboot to
activate the new kernel.
You are now ready to use your tape drive.
8 More Discussions You Might Find Interesting
1. Linux Benchmarks
Notes:
System Configuration: Dell Computer Corporation PowerEdge 4600 (4 X Intel(R) XEON(TM) CPU 2.00GHz
1988.782 MHz) hyperthreaded
System clock frequency: 99.0827 MHz
Memory size (approximate): 2559 Megabytes
========================= CPUs ========================
CPU # CPU... (0 Replies)
Discussion started by: tnorth
0 Replies
2. Linux Benchmarks
CPU/Speed: Dual PIII 533
Ram: 256Mb PC133
Motherboard: Unknown, Intel Chipset
Cache: 256k on board
Controller: PARC Raid 2/Si, AIC-7880U
Disk: 30Gb RAID 5
Load: 1 user. Clean boot, init 5 but X-Windows not loaded.
Kernel: See Benchmarks.
pgms: gcc 3.2.3
... (2 Replies)
Discussion started by: Garp
2 Replies
3. Solaris
hi, i am trying to install solaris 10 (on 4 cd's downloaded from the sun website) on my dell poweredge 2800 server. 2 xeon processors, 2GB of RAM and 2 NICS, 73 GB SCSI (maxtor ultra320, 3.5 series), i can give more details on request...
the installation crashes when trying to detect the NICS... (0 Replies)
Discussion started by: xinugeek
0 Replies
4. Red Hat
I have successfully installed RedHat 8.0 onto a Dell PowerEdge SC1425 today. This server has two SATA hard drives, and an IDE DVD-ROM drive.
Using the following kernel parameters, i successfully installed across both hard drives from CD:
ide0=0x1f0,0x3f6,14 vga=791 resolution=1024x768 expert... (5 Replies)
Discussion started by: fishsponge
5 Replies
5. Filesystems, Disks and Memory
Does anybody no how to get around the fact that the Red Hat installation does not see the SCSI hard drives. It lets you manually pick the proper device, but still fails saying no drive detected (or something to that effect). I was going to install windows 2003 Server and use VMware...but again,... (1 Reply)
Discussion started by: Fatflea
1 Replies
6. UNIX for Dummies Questions & Answers
I have 2 Dell Poweredge 1950 servers running . I have been having intermittent performance issues with the NIC cards on one of them. The two servers are identical and are running the same operating system. The server that has the issue is on the DMZ on a a static IP and is hosting a website. ... (0 Replies)
Discussion started by: skotapal
0 Replies
7. SCO
Hello all,
I'am experiencing weird relyability problems with a SCO 6.0 Openserver server that runs on a Dell Poweredge 1800 equipped with a PERC DC4 raid controller and 4 36 GB 15 K rpm hot swappable scsi harddisks.
It runs a RAID 10 configuration.
It uses the mega hba, Revision 8.03a Release... (1 Reply)
Discussion started by: frederik1
1 Replies
8. Programming
Hi,
I have a C++ program to access /dev/mem and retrieve details like Vendor, Manufacturer details of the motherboard. This works fine on all the machines except for on Dell Poweredge 2850,1950... machines.
I receive a 'EFAULT' when I try to access /dev/mem on these servers.
I suspect some... (1 Reply)
Discussion started by: ragisreekanth
1 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)