Scan for new SAN with FC on suse 9 (SLES9)

 
Thread Tools Search this Thread
Operating Systems Linux SuSE Scan for new SAN with FC on suse 9 (SLES9)
# 1  
Old 01-29-2015
Scan for new SAN with FC on suse 9 (SLES9)

Hi,
I connect the server to new SAN with FC (fiber channel). I run the scan but there is no multipath is installed on the server, how can I see which /dev/dm- is the right one so I can create pv (pvcreate)?Smilie

# cat /etc/SuSE-release
SUSE LINUX Enterprise Server 9 (x86_64)
VERSION = 9
PATCHLEVEL = 3
#

Br
mehhos
Login or Register to Ask a Question

Previous Thread | Next Thread

3 More Discussions You Might Find Interesting

1. Filesystems, Disks and Memory

Faster way: SAN hd to SAN hd copying

hi! i got a rhel 6.3 host that already have an xfs filesystem mounted from a SAN (let's call it SAN-1) whose size is 9TB. i will be receiving another SAN (let's call it SAN-2) storage of 15TB size. this new addition is physically on another SAN storage. SAN-1 is on a Pillar storage while the new... (6 Replies)
Discussion started by: rino19ny
6 Replies

2. AIX

IBM SAN TO SAN Mirroring

Has anyone tried SAN to SAN mirroring on IBM DS SAN Storage. DS5020 mentions Enhanced Remote Mirror to multi-LUN applications I wonder if Oracle High availibility can be setup using Remote Mirror option of SAN ? (1 Reply)
Discussion started by: filosophizer
1 Replies

3. Solaris

Thoughts/experiences of SAN attaching V880 to EMC SAN

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
Login or Register to Ask a Question
MULTIPATH(8)						   Linux Administrator's Manual 					      MULTIPATH(8)

NAME
multipath - Device mapper target autoconfig SYNOPSIS
multipath [-v verbosity] [-d] [-h|-l|-ll|-f|-t|-F] [-p failover|multibus|group_by_serial|group_by_prio|group_by_node_name] [device] DESCRIPTION
multipath is used to detect multiple paths to devices for fail-over or performance reasons and coalesces them OPTIONS
-v level verbosity, print all paths and multipaths 0 no output 1 print the created or updated multipath names only, for use to feed other tools like kpartx 2 + print all info : detected paths, coalesced paths (ie multipaths) and device maps -h print usage text -d dry run, do not create or update devmaps -l show the current multipath topology from information fetched in sysfs and the device mapper -ll show the current multipath topology from all available information (sysfs, the device mapper, path checkers ...) -f flush a multipath device map specified as parameter, if unused -F flush all unused multipath device maps -t print internal hardware table to stdout -p policy force maps to specified policy: failover 1 path per priority group multibus all paths in 1 priority group group_by_serial 1 priority group per serial group_by_prio 1 priority group per priority value. Priorities are determined by callout programs specified as a global, per-con- troller or per-multipath option in the configuration file group_by_node_name 1 priority group per target node name. Target node names are fetched in /sys/class/fc_transport/target*/node_name. device update only the devmap the path pointed by device is in. device is in the /dev/sdb (as shown by udev in the $DEVNAME variable) or major:minor format. device may alternatively be a multipath mapname SEE ALSO
multipathd(8), multipath.conf(5), kpartx(8), udev(8), dmsetup(8) hotplug(8) AUTHORS
multipath was developed by Christophe Varoqui, <christophe.varoqui@free.fr> and others. July 2006 MULTIPATH(8)