USCSICMD ioctl calls for Fibre Channel(FC) devices on Solaris 10?


 
Thread Tools Search this Thread
Operating Systems Solaris USCSICMD ioctl calls for Fibre Channel(FC) devices on Solaris 10?
# 1  
Old 04-08-2010
USCSICMD ioctl calls for Fibre Channel(FC) devices on Solaris 10?

Hi ,

I have wrtitten a C program that issues USCSICMD ioctl call to the tape devices attached on solaris sparc 10. I was able to get the required information from all SCSI tape devices attached using the utility. But, whenever it is run on FC attached tape drives , the program returns an error saying "Inappropriate ioctl for device".

bash-2.05# inquiry /devices/pci@1f,4000/fibre-channel@2/fp@0,0:devctl
inquiry: /devices/pci@1f,4000/fibre-channel@2/fp@0,0:devctl: scsi inquiry failed: Inappropriate ioctl for device

Is it possible to make an USCSICMD ioctl on FC attached tape devices ?. Can someone please provide an example if possible.

Thanks,
Naveen
Login or Register to Ask a Question

Previous Thread | Next Thread

9 More Discussions You Might Find Interesting

1. Solaris

Issue with Fiber Channel cards in Solaris

hi everone i am experiencing disconnectivity from storage to My database machines. i have doubt on my FC cards in my sparc T4-2 machines. i want to know how should i check from my solaris that whether the cards are ok or not because once the disks get disconnect from SAN so it come back again but... (5 Replies)
Discussion started by: janakors
5 Replies

2. Solaris

Fibre Channel link not ready on Netra 240

Hi, One of my Netra 240 went into hung state and I had to reboot it. I powered it off and tried booting it again but unsuccessful. It is not connected to SAN and have local disks. Not able to boot in failsafe mode too. There are two disks of 72GB, both are mirrored in SVM. It complains about... (5 Replies)
Discussion started by: solaris_1977
5 Replies

3. AIX

[ASK] - AIX Fibre Channel behavior

Hello all, Let me introduce about the context and my environment. We have an AIX 6.1 system, it has 4 FC channels / > lsdev -Cc adapter | grep fcs fcs0 Available 23-T1 Virtual Fibre Channel Client Adapter fcs1 Available 23-T1 Virtual Fibre Channel Client Adapter fcs2 Available 23-T1... (14 Replies)
Discussion started by: Phat
14 Replies

4. Solaris

Fibre channel link down on booting Solaris server

Hi I had power issue that affected a server, in which I had power ON the server SPARC T1-B3 running solaris 10. After power on the system stops at ok prompt, them I issued the following commands: {0} ok setenv auto-boot? false auto-boot? = false {0} ok reset-all SPARC T3-1B,... (10 Replies)
Discussion started by: fretagi
10 Replies

5. Hardware

Fibre Channel HBA recommendations?

We will be buying new Xeon E5-based servers for our datacenter and were wondering which Fibre Channel host bus adapters we should select for these. The choices are Emulex or QLogic (8Gb FC HBAs). Anybody have any recommendations on which is the better choice? Thanks in advance. (1 Reply)
Discussion started by: atahmass
1 Replies

6. AIX

Power6 Virtual Fibre Channel Adapter

Hello, Searched in all IBM Redbooks and on the internet and couldn't find anything about the new feature of POWER 6 which Virtual Fibre ( Fiber ) channel adapter. It is similar to virtual scsi adapter. In my client partition I created the virtual Fibre Adapter mapped it with the VIO... (1 Reply)
Discussion started by: filosophizer
1 Replies

7. AIX

Fibre channel drivers on RS/6000 aix 5L

Want to configure IBM raid strorage but the aix 5L cds do not have the drivers for the fibre channels. The machine is RS/6000. I have gone to IBM downlaodable sites but i can't find the drivers? help pliz:mad: (4 Replies)
Discussion started by: Zim-Aix-Guru
4 Replies

8. IP Networking

Identification of data calls & voice calls

Is there any facility to filter/identify the data calls and voice calls coming throug modem? OR Can we get the data or voice calls information through a script(preferably C Kermit)? (0 Replies)
Discussion started by: pcsaji
0 Replies

9. Solaris

devices in solaris 10

i want to use the devfsadm command and understand its function (3 Replies)
Discussion started by: bondoq
3 Replies
Login or Register to Ask a Question
scsi_tape(7)						 Miscellaneous Information Manual					      scsi_tape(7)

NAME
scsi_tape - SCSI sequential access device driver DESCRIPTION
SCSI sequential-access (tape) devices store a sequence of data blocks. Data can be read and written using either fixed or variable sized block mode. If supported by the device, variable sized block mode is normally used (even when all blocks are the same size). Fixed sized block mode is generally only used for tape devices which do not support variable sized blocks. Fixed sized block mode can be used on some tape devices which support variable sized blocks to increase I/O performance. Generally SCSI tape devices are controlled through the (see mt(7)) generic tape device interface. This section describes features that are specific to SCSI tape devices. The ioctl (see scsi(7)) can be used to determine remaining tape capacity for some tape devices. The field indicates the "natural" block size of the device. This value may or may not be the current block size of the device. The number of blocks, indicated by the field, is an estimate of how much data can be written on the remaining media. A zero size is returned for devices that do not provide remaining- capacity information. The quantity of data that can actually be written may be higher or lower than indicated, depending on such factors as block size, media defects, data compression, and ability to maintain streaming. To improve performance, most SCSI tape devices have caches. Read-cache use, called "read ahead", causes the tape drive to read data in anticipation of read requests. Read ahead is only apparent to users in the increased performance that it produces. Write-cache use is called "immediate reporting". Immediate reporting increases I/O performance by reporting a completed write status before the data being written is actually committed to media. This allows the application program to supply additional data so that continuous media motion, called "streaming", can be achieved. The ioctl can be used to determine if immediate-reporting functionality is currently being used by the device. The value "1" indicates immediate reporting is enabled. By default, the device driver attempts to enable immediate reporting. The ioctl can be used to explicitly enable or disable immediate reporting. A zero value disables immediate reporting. The value "1" enables immediate reporting. The ioctl command can be used to cause any cached data to be written (committed) to media. Note that the device immediate reporting mode set by the ioctl survives between and calls, but not through system reboot. The ioctl indicates the device's current block size. A block size of zero indicates the device is in variable-sized-block mode. A non- zero block size indicates the device is in fixed-sized-block mode. The ioctl changes the current block size to the specified number of bytes. Setting the block size to zero specifies that variable-sized- block mode should be used. Any non-zero block size specifies that fixed-sized-block mode should be used. By default, the device driver attempts to set the block size to zero during open. If variable-sized-block mode is not supported by the device, the driver selects an appropriate block size for fixed-sized-block mode use. Note that the device block size set by the ioctl survives between and calls, but not through system reboot. The ioctl indicates the device's maximum and minimum fixed block-size limits. The device's minimum fixed block size is indicated by the field. The field contains the smaller of the maximum block size supported by the device and the maximum block size supported by the system This is the largest valid block size for the specific combination of device, driver, and host system being used. The ioctl can be used to determine the current media position for some devices. For devices that support this capability, the resultant value can be used to reposition the media to the same position in the future. The ioctl can be used to cause media repositioning on some devices. For devices that support this capability, media repositioning via this mechanism can generally be completed more quickly than might be similarly accomplished using record, filemark, or setmark spacing. The argument value specified should be the result of a previous for that media volume. The following is included from /* ioctl support for SCSI tape commands */ #define SIOC_GET_IR _IOR('S', 14, int) #define SIOC_SET_IR _IOW('S', 15, int) #define SIOC_GET_BLOCK_SIZE _IOR('S', 30, int) #define SIOC_SET_BLOCK_SIZE _IOW('S', 31, int) #define SIOC_GET_BLOCK_LIMITS _IOW('S', 32, struct scsi_block_limits) #define SIOC_GET_POSITION _IOR('S', 33, int) #define SIOC_SET_POSITION _IOW('S', 34, int) /* structure for SIOC_GET_BLOCK_LIMITS ioctl */ struct scsi_block_limits { unsigned min_blk_size; unsigned max_blk_size; }; WARNINGS
SCSI bus and device resets cause some devices to reposition media to beginning-of-tape (BOT). This unintentional media repositioning can cause loss of data. The driver causes the first subsequent attempt to fail as an indication of potential data loss. The driver does not write filemarks at close if the media has been programmatically repositioned. Applications that reposition the media prior to closing the device should write any required tapemarks. SEE ALSO
mknod(1M), mt(7), scsi(7). scsi_tape(7)