09-23-2013
In most cases, except possibly for some (small minority) HBAs, they'll show up as normal SCSI drives (sdX) once probe/scanned.
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
LEARN ABOUT DEBIAN
tapset::perf
TAPSET::PERF(3stap) TAPSET::PERF(3stap)
NAME
tapset::perf - systemtap perf probe points
DESCRIPTION
This family of probe points is used to probe "perf events" on suitably configured kernels (2.6.33+). It contains a number of aliases for
the ABI-specified event type/config tuples.
The default sampling interval of the translator(1000000) is not overridden, so some of these probe points may fire very infrequently. Use
the lower level perf.type(AA).config(BB).sample(CC) probe point if this is a problem.
perf.hw.*
A variety of hardware events, as generalized by the kernel. These generally require running on bare hardware with selected proces-
sors.
probe perf.hw.cpu_cycles
probe perf.hw.instructions
probe perf.hw.cache_references
probe perf.hw.cache_misses
probe perf.hw.branch_instructions
probe perf.hw.branch_misses
probe perf.hw.bus_cycles
perf.sw.*
Special "software" events provided by the kernel. These sometimes work in virtualized environments and with more processor archi-
tectures.
probe perf.sw.cpu_clock
probe perf.sw.task_clock
probe perf.sw.page_faults
probe perf.sw.context_switches
probe perf.sw.cpu_migrations
probe perf.sw.page_faults_min
probe perf.sw.page_faults_maj
probe perf.sw.alignment_faults
probe perf.sw.emulation_faults
perf.hw_cache.TYPE.ACCESS.RESULT
Hardware cache events, where available. A subset of the following cartesian product may be available:
probe perf.hw_cache.l1d.*.*
probe perf.hw_cache.l1i.*.*
probe perf.hw_cache.ll.*.*
probe perf.hw_cache.dtlb.*.*
probe perf.hw_cache.itlb.*.*
probe perf.hw_cache.bpu.*.*
probe perf.hw_cache.*.read.*
probe perf.hw_cache.*.write.*
probe perf.hw_cache.*.prefetch.*
probe perf.hw_cache.*.*.access
probe perf.hw_cache.*.*.miss
SEE ALSO
stap(1), stapprobes(3stap)
IBM
TAPSET::PERF(3stap)