Sponsored Content
Full Discussion: FC related disks
Special Forums Hardware Filesystems, Disks and Memory FC related disks Post 302480406 by Tlogine on Tuesday 14th of December 2010 09:29:54 PM
Old 12-14-2010
FC related disks

Dear Friends,

I would like know what are FC related disks and how it will be viewed by generic OSes (Unix, Unix like, Windows & etc.)

AFAIK it is viewed by generic OS as SCSI.

Can we have FC related disks as internal storage(physically) of general purpose machine (Server / PC / Laptop)

Thank you.
 

9 More Discussions You Might Find Interesting

1. UNIX for Dummies Questions & Answers

how many disks do I have?

Hi How do I check how many disks do I have in Solaris & HP-UX? Also what does this mean c9t1d5 in /dev/dsk what is c, t, d etc cheers (8 Replies)
Discussion started by: g-e-n-o
8 Replies

2. UNIX for Advanced & Expert Users

CPIO related

i have a cpio.z file containing another cpio file . I want to view the contents of the cpio file inside . How to do it? my parent cpio file invoked with cpio -itv looks some thing like ompmum4 sbadgire> zcat 210_2122_ECP_03.cpio.Z| cpio -itv -rwxr-xr-x 1 20519 20519 761856... (1 Reply)
Discussion started by: rraajjiibb
1 Replies

3. UNIX for Dummies Questions & Answers

Unix Related

well through my 6 months education i know some unix os but i can't find one for my p3 via board can any one tell me where to find such please replay as email or private msg and thanks (3 Replies)
Discussion started by: JaMaL
3 Replies

4. Solaris

Re-using disks

I would like to know if I can move the disks from a V240 chassis into a V440 chassis to use the increased resources (CPU & Memory) to boost performance. I know you can move disks between V210/240 chassis's, but I'm not sure if this would work between 240s & 440s. Any help would be much appreciated. (4 Replies)
Discussion started by: Chains
4 Replies

5. Solaris

related to mounting.......

can i mount the same mount point to two different file system...... (4 Replies)
Discussion started by: sudhansu
4 Replies

6. Shell Programming and Scripting

Scripting related .

Could any body give the solution/script to get the below... 1.script will run and detcect the files having 0kb size , and give the solution in a out put file.(Will search the file in the path let say /abc/M/) 2.Same as the above also send a mail to your mails id , with the file name stating... (13 Replies)
Discussion started by: alexMar
13 Replies

7. Shell Programming and Scripting

need downloading related help...but its not related to unix

Hi All, I am trying to dowmload the zip file "zkManageCustomers.zip " but i dont have access. Can anyone help me to download this file See the below link- http://www.ibm.com/developerworks/opensource/library/wa-aj-open/index.html?ca=drs- Please help me as early as... (1 Reply)
Discussion started by: aish11
1 Replies

8. UNIX for Dummies Questions & Answers

Question related to 'ps'

If I run a script called 'abc.sh' and then execute the following : ps -ef | grep 'abc.sh' I always get two rows of output, one for the executing script, and the other for the grep command that I have triggered after the pipe. Questions: Why does the second row turn up in the results. My... (10 Replies)
Discussion started by: jawsnnn
10 Replies

9. Shell Programming and Scripting

Mail related

I have maintaining 16 client PCs.I want to get a mail from client PCs whenever any one of the services are not working.Services like postgres ,sms , jts and synch etc.,The Client PCs are remotely placed.I want to develop this through shell script ,But I don't have an idea to develop this... (2 Replies)
Discussion started by: kannansoft1985
2 Replies
lsscsi(8)							      LSSCSI								 lsscsi(8)

NAME
lsscsi - list SCSI devices (or hosts) and their attributes SYNOPSIS
lsscsi [--classic] [--device] [--generic] [--help] [--hosts] [--kname] [--list] [--long] [--protection] [--sysfsroot=PATH] [--transport] [--verbose] [--version] [H:C:T:L] DESCRIPTION
Uses information in sysfs (linux kernel series 2.6 and later) to list scsi devices (or hosts) currently attached to the system. Options can be used to control the amount and form of information provided for each device. If a H:C:T:L argument is given then it acts as a filter and only devices that match it are listed. The colons don't have to be present, and '-', '*', '?' or missing arguments at the end are interpreted as wildcards. '-' needs to stand alone or else it is taken as the beginning of an option (e.g. '-:-:-:-' is illegal). '*' needs to be escaped from the shell. A leading '[' and trailing ']' are permitted (e.g. '[1:0:0]' matches all luns on 1:0:0). May also be used to filter --hosts in which case only the H is active and may be either a number or in the form "host<n>" where <n> is a host number. By default in this utility device node names (e.g. "/dev/sda" or "/dev/root_disk") are obtained by noting the major and minor numbers for the listed device obtained from sysfs (e.g. the contents of "/sys/block/sda/dev") and then looking for a match in the "/dev" directory. This "match by major and minor" will allow devices that have been given a different name by udev (for example) to be correctly reported by this utility. In some situations it may be useful to see the device node name that linux would produce by default, so the --kname option is provided. An example of where this may be useful is kernel error logs which tend to report disk error messages using the disk's default kernel name. Information about this utility including examples can also be found at: http://sg.danny.cz/scsi/lsscsi.html . OPTIONS
-c, --classic The output is similar to that obtained from 'cat /proc/scsi/scsi' -d, --device After outputting the (probable) scsi device name the device node major and minor numbers are shown in brackets (e.g. "/dev/sda[8:0]"). -g, --generic Output the scsi generic device file name. Note that if the sg driver is a module it may need to be loaded otherwise '-' may appear. -h, --help Output the usage message and exit. -H, --hosts List the SCSI hosts currently attached to the system. If this option is not given then SCSI devices are listed. -k, --kname Use linux default algorithm for naming devices (e.g. block major 8, minor 0 is "/dev/sda") rather than the "match by major and minor" in the "/dev" directory as discussed above. -L, --list Output additional information in <attribute_name>=<value> pairs, one pair per line preceded by two spaces. This option has the same effect as '-lll' -l, --long Output additional information for each SCSI device (host). Can be used multiple times for more output in which case the shorter option form is more convenient (e.g. '-lll'). When used three times (i.e. '-lll') outputs SCSI device (host) attributes one per line; preceded by two spaces; in the form "<attribute_name>=<value>". -p, --protection Output additional data integrity (protection) information. -t, --transport Output transport information. This will be a target related information or, if --hosts is given, initiator related information. When used without --list, a name or identifier (or both) are output on a single line, usually prefixed by the type of transport. For devices this information replaces the normal vendor, product and revision strings. When the --list option is also given then addi- tionally multiple lines of attribute_name=value pairs are ouput, each indented by two spaces. See the section on transports below. -v, --verbose outputs directory names where information is found. Use multiple times for more output. -V, --version outputs version information then exits. -y, --sysfsroot=PATH assumes sysfs is mounted at PATH instead of the default '/sys' . If this option is given PATH should be an absolute path (i.e. start with '/'). NOTES
Information for this command is derived from the sysfs file system, which is assumed to be mounted at /sys unless specified otherwise by the user. SCSI (pseudo) devices that have been detected by the SCSI mid level will be listed even if the required upper level drivers (i.e. sd, sr, st, osst or ch) have not been loaded. If the appropriate upper level driver has not been loaded then the device file name will appear as '-' rather than something like '/dev/st0'. Note that some devices (e.g. scanners and medium changers) do not have a primary upper level driver and can only be accessed via a scsi generic (sg) device name. lsscsi version 0.21 or later is required to correctly display SCSI devices in linux kernel 2.6.26 (and possibly later) when the CON- FIG_SYSFS_DEPRECATED_V2 kernel option is not defined. TRANSPORTS
This utility lists SCSI devices which are known as logical units (lu) in the SCSI Architecture Model (ref: SAM-4 at http://www.t10.org) or hosts when the --hosts option is given. A host is called an initiator in SAM-4. A SCSI command travels out via an initiator, across some transport to a target and then onwards to a logical unit. A target device may contain several logical units. A target device has one or more ports that can be viewed as transport end points. Each FC and SAS disk is a single target that has two ports and contains one logical unit. If both target ports on a FC or SAS disk are connected and visible to a machine, then lsscsi will show two entries. Initiators (i.e. hosts) also have one or more ports and some HBAs in Linux have a host entry per initiator port while others have a host entry per initiator device. When the --transport option is given for devices (i.e. --hosts not given) then most of the information produced by lsscsi is associated with the target, or more precisely: the target port, through which SCSI commands pass that access a logical unit. Typically this utility provides one line of output per "device" or host. Significantly more information can be obtained by adding the --list option. When used together with the --transport option, after the summary line, multiple lines of transport specific information in the form "<attribute_name>=<value>" are output, each indented by two spaces. Using a filter argument will reduce the volume of output if a lot of devices or hosts are present. The transports that are currently recognized are: IEEE 1394, ATA, FC, iSCSI, SAS, SATA, SPI and USB. For IEEE 1394 (a.k.a. Firewire and "SBP" when storage is involved), the EUI-64 based target port name is output when --transport is given, in the absence of the --hosts option. When the --hosts option is given then the EUI-64 initiator port name is output. Output on the summary line specific to the IEEE 1394 transport is prefixed by "sbp:". to detect ATA and SATA a crude check is performed on the driver name (after the checks for other transports are exhausted). Based on the driver name either ATA or SATA transport type is chosen. Output on the summary line is either "ata:" or "sata:". No other attributes are given. Most device and hosts flagged as "ata:" will use the parallel ATA transport (PATA). For Fibre Channel (FC) the port name and port identifier are output when --transport is given. In the absence of the --hosts option these ids will be for the target port associated with the device (logical unit) being listed. When the --hosts option is given then the ids are for the initiator port used by the host. Output on the summary line specific to the FC transport is prefixed by "fc:". For iSCSI the target port name is output when --transport is given, in the absence of the --hosts option. This is made up of the iSCSI name and the target portal group tag. Since the iSCSI name starts with "iqn" no further prefix is used. When the --hosts option is given then only "iscsi:" is output on the summary line. For Serial Attached SCSI the SAS address of the target port (or initiator port if --hosts option is also given) is output. This will be a naa-5 address. For SAS HBAs and SAS targets (such as SAS disks and tape drives) the SAS address will be world wide unique. For SATA disks attached to a SAS expander, the expander provides the SAS address by adding a non zero value to its (i.e. the expander's) SAS address (e.g. expander_sas_address + phy_id + 1). SATA disks directly attached to SAS HBAs seem to have an indeterminate SAS address. Output on the sum- mary line specific to the SAS transport is prefixed by "sas:". For the SCSI Parallel Interface (SPI) the target port identifier (usually a number between 0 and 15 inclusive) is output when --transport is given, in the absence of the --hosts option. When the --hosts option is given then only "spi:" is output on the summary line. When a USB transport is detected, the summary line will contain "usb:" followed by a USB device name. The USB device name has the form "<b>-<p1>[.<p2>[.<p3>]]:<c>.<i>" where <b> is the USB bus number, <p1> is the port on the host. <p2> is a port on a host connected hub, if present. If needed <p3> is a USB hub port closer to the USB storage device. <c> refers to the configuration number while <i> is the inter- face number. There is a separate SCSI host for each USB (SCSI) target. A USB SCSI target may contain multiple logical units. Thus the same "usb: <device_name>" string appears for a USB SCSI host and all logical units that belong to the USB SCSI target associated with that USB SCSI host. AUTHOR
Written by Doug Gilbert REPORTING BUGS
Report bugs to <dgilbert at interlog dot com>. COPYRIGHT
Copyright (C) 2003-2009 Douglas Gilbert This software is distributed under the GPL version 2. There is NO warranty; not even for MERCHANTABILITY or FITNESS FOR A PARTICULAR PUR- POSE. SEE ALSO
lspci lsusb lsscsi-0.23 November 2009 lsscsi(8)
All times are GMT -4. The time now is 10:18 AM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy