Linux and UNIX Man Pages

Linux & Unix Commands - Search Man Pages

scsi_mode_select(9) [centos man page]

SCSI_MODE_SELECT(9)						  SCSI mid layer					       SCSI_MODE_SELECT(9)

scsi_mode_select - issue a mode select SYNOPSIS
int scsi_mode_select(struct scsi_device * sdev, int pf, int sp, int modepage, unsigned char * buffer, int len, int timeout, int retries, struct scsi_mode_data * data, struct scsi_sense_hdr * sshdr); ARGUMENTS
sdev SCSI device to be queried pf Page format bit (1 == standard, 0 == vendor specific) sp Save page bit (0 == don't save, 1 == save) modepage mode page being requested buffer request buffer (may not be smaller than eight bytes) len length of request buffer. timeout command timeout retries number of retries before failing data returns a structure abstracting the mode header data sshdr place to put sense data (or NULL if no sense to be collected). must be SCSI_SENSE_BUFFERSIZE big. DESCRIPTION
Returns zero if successful; negative error number or scsi status on error AUTHORS
James Bottomley <> Author. Rob Landley <> Author. COPYRIGHT
Kernel Hackers Manual 3.10 June 2014 SCSI_MODE_SELECT(9)

Check Out this Related Man Page

FC_REMOTE_PORT_ADD(9)						  SCSI mid layer					     FC_REMOTE_PORT_ADD(9)

fc_remote_port_add - notify fc transport of the existence of a remote FC port. SYNOPSIS
struct fc_rport * fc_remote_port_add(struct Scsi_Host * shost, int channel, struct fc_rport_identifiers * ids); ARGUMENTS
shost scsi host the remote port is connected to. channel Channel on shost port connected to. ids The world wide names, fc address, and FC4 port roles for the remote port. DESCRIPTION
The LLDD calls this routine to notify the transport of the existence of a remote port. The LLDD provides the unique identifiers (wwpn,wwn) of the port, it's FC address (port_id), and the FC4 roles that are active for the port. For ports that are FCP targets (aka scsi targets), the FC transport maintains consistent target id bindings on behalf of the LLDD. A consistent target id binding is an assignment of a target id to a remote port identifier, which persists while the scsi host is attached. The remote port can disappear, then later reappear, and it's target id assignment remains the same. This allows for shifts in FC addressing (if binding by wwpn or wwnn) with no apparent changes to the scsi subsystem which is based on scsi host number and target id values. Bindings are only valid during the attachment of the scsi host. If the host detaches, then later re-attaches, target id bindings may change. This routine is responsible for returning a remote port structure. The routine will search the list of remote ports it maintains internally on behalf of consistent target id mappings. If found, the remote port structure will be reused. Otherwise, a new remote port structure will be allocated. Whenever a remote port is allocated, a new fc_remote_port class device is created. Should not be called from interrupt context. NOTES
This routine assumes no locks are held on entry. AUTHORS
James Bottomley <> Author. Rob Landley <> Author. COPYRIGHT
Kernel Hackers Manual 3.10 June 2014 FC_REMOTE_PORT_ADD(9)
Man Page

4 More Discussions You Might Find Interesting

1. Solaris

Unable to install Sol10 on V245, exiting to shell.

Hi there, OK so I am super-green, but I have a problem I am hoping someone can help me with. I have a V245 that I am unable to install Solaris 10 (10/09) onto as during the initial install process, the UI pops up for region selection, but then as I enter my region, identify the system, up comes... (21 Replies)
Discussion started by: wallrunn3r
21 Replies

2. Solaris

Different disk size on different controllers

Hi folks, I just recently build myself a NAS with Oracle Solaris 11 Express. MOBO: Asus M4N68T-M LE V2 nForce 630a AM3 PCI-e Controller: 2x Exsys EX-3503 with Sil3132 Chipset (latest FW) HDD: 7x 2000GB Samsung EcoGreen F4 HD204UI 32MB 3.5" (latest FW) OS: SunOS zaruba 5.11 snv_151a i86pc... (4 Replies)
Discussion started by: Garter
4 Replies

3. Solaris

cannot label 'c0t5000CCA0251EF65Cd0': EFI labeled devices are not supported on root pools

I'm running Solaris 10 u9. I just applied the April quarterly patch cluster. I'm trying to mirror the boot disk which is using zfs, something I've done before w/o problems prior to the patch cluster install. disk=c0t5000CCA0251D9514d0;mirrordisk=c0t5000CCA0251EF65Cd0;echo $disk $mirrordisk... (7 Replies)
Discussion started by: TKD
7 Replies

4. Solaris

Missing ASM Disks in Solaris 11.3 LDOM

Hi Guys, Just a quick question hopefully someone will have seen this before and will be able to enlighten me. I have been doing some Infrastructure Verification Testing and one of the tests was booting the primary domain from alternate disks, this all went well - however on restarting one of... (7 Replies)
Discussion started by: gull04
7 Replies