03-12-2009
'devices.fcp.changer' is probably a generic message rather than an actual fileset.
cfgmgr is a bit like that, it will just guess a fileset name if it detects a device and cannot configure it.
you need to find out what the end device, rmt0, is and then contact the manufacturer for the AIX driver.
If it is an IBM drive then the Atape driver will probably do the job (google atape for more info). If it is a non-IBM drive then contact the manufacturer or search their web site for drivers.
10 More Discussions You Might Find Interesting
1. AIX
Currently I have a Dell Ultrium LTO 2 Tape Drive. I am going to have a IBM AIX server. Just wonder if it is possibe to connect this tape drive to the aix server? I have Brightstor Arcserver installed on another win 2003 server. Is it possible to install the arcserve agent on the aix and use the... (1 Reply)
Discussion started by: ming413
1 Replies
2. AIX
I am having my 14 Aix 5.3 servers on bladecenters connected with my Tape Library.
I had a backup scheduled on tape library but after taking backup successfully,
Now,
Question 1:-
I wanted to restore backup but tape library could not recognize the tape and I get I/O error in TSM. I think it... (0 Replies)
Discussion started by: Shrek
0 Replies
3. AIX
Hi,
My situation is to write a backup script for AIX server which doesnt have a tape mounted.
They have created a folder on windows so that all AIX backup files can be moved to that windows folder where they will put these AIX backup files on a tape.
Appreciate help.
Regards
dsrules. (7 Replies)
Discussion started by: dsrules
7 Replies
4. AIX
Hi,
Can anyone tell how to list files in a AIX 3.2 mksysb backup tape.
Thanks!
Victor Cheung (4 Replies)
Discussion started by: victorcheung
4 Replies
5. AIX
Hi all. I hope someone could give me a hand on installing Backup Exec agent on AIX machine :(
Agent:
OS: AIX 5.3
Hostname: DB-HN-SRV02
IP: 10.1.4.64
Backup server:
OS: Windows Server 2003
Hostname: backup-srv
IP: 10.1.5.51
I download "Legacy Unix agent.tar", untar, then run file... (0 Replies)
Discussion started by: bsddaemon
0 Replies
6. AIX
Hi all,
I have a problem here
root@host1 / # lsdev -Cc tape
rmt0 Defined 07-00-02 IBM 3580 Ultrium Tape Drive (FCP)
rmt1 Defined 07-00-02 IBM 3580 Ultrium Tape Drive (FCP)
smc0 Defined 07-00-02 IBM 3573 Tape Medium Changer (FCP)
root@host1 / # cfgmgr -l fcs2
Method error... (2 Replies)
Discussion started by: h@foorsa.biz
2 Replies
7. AIX
I am trying to use this command to eject the tape
mt -f /dev/rmt/0 unload
but it gives me error
mt -f /dev/rmt/0 unload
mt: 0511-575 unload is not a recognized subcommand.
Usage: mt Subcommand
Valid subcommands are:
weof
eof
fsf
bsf
... (5 Replies)
Discussion started by: filosophizer
5 Replies
8. AIX
Hi,
We have backup on LTO-3 tape it was taken from windows via windows backup utility,
now the issue is that we want to list the content of tape in aix 6.1. Kindly help.
Regards
Salman (3 Replies)
Discussion started by: salmanraza
3 Replies
9. UNIX for Advanced & Expert Users
Hi All,
Seeking information on the following and perhaps a bit of insight and opinions:
I would like to look into using NDMP to backup a disk array using NetBackup 7.5 to HP B6200 StoreOnce Backup System (i.e. Virtual Tape Library) as well as physical tape library.
Does anyone think... (0 Replies)
Discussion started by: zixzix01
0 Replies
10. AIX
Good day!
Need help in checking my AIX 7.1 box.
After we have finished zoning our TS3200 and TS3310 tape libraries, we installed the Atape driver,
# lslpp -L |grep tape
Atape.driver 11.7.7.0 C F IBM AIX Enhanced Tape and
devices.fcp.tape.rte 7.1.3.15 C ... (0 Replies)
Discussion started by: alainken3
0 Replies
CD(9) BSD Kernel Developer's Manual CD(9)
NAME
cd -- CDROM driver for the CAM SCSI subsystem
DESCRIPTION
The cd device driver provides a read only interface for CDROM drives (SCSI type 5) and WORM drives (SCSI type 4) that support CDROM type com-
mands. Some drives do not behave as the driver expects. See the QUIRKS section for information on possible flags.
QUIRKS
Each CD-ROM device can have different interpretations of the SCSI spec. This can lead to drives requiring special handling in the driver.
The following is a list of quirks that the driver recognize.
CD_Q_NO_TOUCH This flag tells the driver not to probe the drive at attach time to see if there is a disk in the drive and find out what
size it is. This flag is currently unimplemented in the CAM cd driver.
CD_Q_BCD_TRACKS This flag is for broken drives that return the track numbers in packed BCD instead of straight decimal. If the drive seems
to skip tracks (tracks 10-15 are skipped) then you have a drive that is in need of this flag.
CD_Q_NO_CHANGER This flag tells the driver that the device in question is not a changer. This is only necessary for a CDROM device with
multiple luns that are not a part of a changer.
CD_Q_CHANGER This flag tells the driver that the given device is a multi-lun changer. In general, the driver will figure this out auto-
matically when it sees a LUN greater than 0. Setting this flag only has the effect of telling the driver to run the initial
read capacity command for LUN 0 of the changer through the changer scheduling code.
CD_Q_10_BYTE_ONLY
This flag tells the driver that the given device only accepts 10 byte MODE SENSE/MODE SELECT commands. In general these
types of quirks should not be added to the cd(4) driver. The reason is that the driver does several things to attempt to
determine whether the drive in question needs 10 byte commands. First, it issues a CAM Path Inquiry command to determine
whether the protocol that the drive speaks typically only allows 10 byte commands. (ATAPI and USB are two prominent exam-
ples of protocols where you generally only want to send 10 byte commands.) Then, if it gets an ILLEGAL REQUEST error back
from a 6 byte MODE SENSE or MODE SELECT command, it attempts to send the 10 byte version of the command instead. The only
reason you would need a quirk is if your drive uses a protocol (e.g., SCSI) that typically does not have a problem with 6
byte commands.
FILES
/sys/cam/scsi/scsi_cd.c is the driver source file.
SEE ALSO
cd(4), scsi(4)
HISTORY
The cd manual page first appeared in FreeBSD 2.2.
AUTHORS
This manual page was written by John-Mark Gurney <jmg@FreeBSD.org>. It was updated for CAM and FreeBSD 3.0 by Kenneth Merry
<ken@FreeBSD.org>.
BSD
March 25, 2014 BSD