09-22-2013
I'm asking how san devices are represented ..... For example. If we want to know the scsi devices in fdisk -l ..... They are represented as sda,sdb,etc..... In the same way.... How SAN devices are represented........??
10 More Discussions You Might Find Interesting
1. Solaris
Hi everyone,
I wonder if I can canvas any opinions or thoughts (good or bad) on SAN attaching a SUN V880/490 to an EMC Clarion SAN?
At the moment the 880 is using 12 internal FC-AL disks as a db server and seems to be doing a pretty good job. It is not I/O, CPU or Memory constrained and the... (2 Replies)
Discussion started by: si_linux
2 Replies
2. Shell Programming and Scripting
Hi,
I haven't done this for awhile, and further, I've never done it in perl so I appreciate any help you can give me.
I have a file of lines, each with 5 data points that look like this:
AB,N,ALLIANCEBERNSTEIN HLDNG L.P,AB,N
ALD,N,ALLIED CAPITAL CORPORATION,ALD,N
AFC,N,ALLIED CAPITAL... (4 Replies)
Discussion started by: Pcushing
4 Replies
3. UNIX for Dummies Questions & Answers
Hello everybody,
I'm using the binary inqraid (Linux RHEL) in order to retrieve information about SAN disks. The questions are:
Given an LDEV, how do I know if the SAN disk related to this LDEV is being used by the OS? I mean, how can I demonstrate to "Storage department" that all disks of... (4 Replies)
Discussion started by: asanchez
4 Replies
4. Red Hat
Hello,
How can I identify SAN disks not in use by the OS?
Thank you. (8 Replies)
Discussion started by: asanchez
8 Replies
5. Solaris
How to identify the server is BOOT FROM SAN.
Also how one can find from which device it is booted?
Thanks
Rahul
Double post, continued here (0 Replies)
Discussion started by: rahul.kurumkar
0 Replies
6. Red Hat
Hi, I have many servers all of these are boot from SAN. Can anybody let me know that how to identify the server is Boot fron SAN and from which device?
Thanks
Rahul (1 Reply)
Discussion started by: rahul.kurumkar
1 Replies
7. BSD
Hello,
MBR partition table made by linux fdisk looks certainly not correct when printed by openbsd fdisk:
Partition table created on linux (centos 6.3):
# fdisk -l /dev/sdc
Disk /dev/sdc: 10.7 GB, 10737418240 bytes
255 heads, 63 sectors/track, 1305 cylinders
Units = cylinders of 16065 *... (2 Replies)
Discussion started by: vilius
2 Replies
8. Shell Programming and Scripting
Hi ,
I am trying to filter out the below output of fdisk -l command :
fdisk -l
Disk /dev/sda: 42.9 GB, 42949672960 bytes
255 heads, 63 sectors/track, 5221 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes
Device Boot Start End Blocks Id System
/dev/sda1 ... (9 Replies)
Discussion started by: omkar.jadhav
9 Replies
9. Red Hat
Hello,
1 ) Fdisk -l # Displays all the disk with partition table information
My Query )
A ) How can i make one disk ex: /dev/sdd not visible in fdisk -l output ?
B) From where fdisk -l collect and display the information ? (8 Replies)
Discussion started by: saurabh84g
8 Replies
10. Solaris
I am working on VM host and collecting data to identify the type of storage attached to the server which will be migrated to VNX.
it has one ldom created on it
luxadm probe output ---
No Network Array enclosures found in /dev/es
Found Fibre Channel device(s):
Node... (7 Replies)
Discussion started by: kpatel786
7 Replies
ib(4) File Formats ib(4)
NAME
ib - InfiniBand device driver configuration files
DESCRIPTION
The InfiniBand (IB) bus is an I/O transport based on switched fabrics. IB devices are managed by the ib(7D) nexus driver. There are three
categories of InfiniBand devices:
o IB port/IB VPPA/IB HCA_SVC devices
o IB IOC devices
o IB Psuedo devices
The IB port/IB VPPA/IB HCA_SVC devices are enumerated by way of the ib.conf file. See ib(7D).
The IB IOC devices are enumerated using the InfiniBand Device management class. See ibdm(7D).
For devices not in these two categories, most notably IB Psuedo devices, the driver must provide configuration files to inform the system
of the IB devices to be created. Configuration parameters are represented in the form of name value pairs you can retrieve using the DDI
property interfaces. See ddi_prop_op(9F) for details.
Configuration files for IB device drivers must identify the parent driver explicitly as "ib," and must create a string array property
called "unit-address" which is unique to this entry in the configuration file. Drivers name "ibport" and "ioc" are reserved by ib(7D) and
should not be used.
Each entry in the configuration file creates a prototype devinfo node. Each node is assigned a unit address which is determined by the
value of the "unit-address" property. This property is only applicable to children of the IB parent and is required. See driver.conf(4)
for further details on configuration file syntax.
EXAMPLES
Example 1: Sample configuration file
Here is a configuration file called ibgen.conf for an IB device driver that implements a generic IB driver. This file creates a node
called "ibgen."
#
# Copyright 2002-2003 Sun Microsystems, Inc. All rights reserved.
# Use is subject to license terms.
#
#ident "@(#)ibgen.conf 1.3 03/05/01 SMI"
name="ibgen" parent="ib" unit-address="0";
SEE ALSO
driver.conf(4), ib(7D), ibtl(7D), ddi_prop_op(9F)
SunOS 5.10 19 Feb 2004 ib(4)