[ale] Suse migrations II

Tue Apr 19 12:56:38 EDT 2011

It appears from a quick search that the sddlmag1 device is likely the
HDLM stuff I mentioned before.   I found /dev/hddlmag which led me to
this link:

http://www.google.com/url?sa=t&source=web&cd=6&ved=0CDUQFjAF&url=ftp%3A%
2F%2Fits.utoronto.ca%2Fdocs%2F9985V%2FST9985V%2520Product%2520Documentat
ion%2520Library%2F9900%2FHiCommand%2520Dynamic%2520Link%2520Manager%2520
(HDLM)%2520for%2520Linux%2520User%2520Guide.pdf&rct=j&q=%2Fdev%2Fsddlmag
&ei=qb2tTc7xIajg0gGD-NWhCw&usg=AFQjCNHPpF4z0UWw0ryL2Rlc-uPFBGfLdA&cad=rj
a

Essentially I believe it is Hitachi's software for multipathing as
opposed to the native multipathing on Linux.   As I noted in an earlier
post we opted not to use HDLM so I can't really give you much guidance
on it so hopefully the above will help.   Also there may be more
information on Hitachi's site.

________________________________

From: ale-bounces at ale.org [mailto:ale-bounces at ale.org] On Behalf Of
Damon Chesser
Sent: Tuesday, April 19, 2011 12:03 PM
To: ale at ale.org
Subject: [ale] Suse migrations II

Here is my problem:  I have 7 mount that are from FC on a hitatchi.
Suse 10.2 on a HP server (6 series?) with two qlogic cards.

I have one phys. Drive presented on the server /dev/ccsis/c0d0

LVM is in use, everything is mounted as a LV except for /boot and /root
on c0d0 (c0d0p1, c0d0p2)

I can run vgdisplay -v FOO and find out what "drive" FOO is mounted on:
in part:

--- Logical volume ---

  LV Name                /dev/FOO/FOO

 VG Name                FOO

  LV UUID                ZC0ZlW-UK4r-TC6j-Yvj2-qf7Y-34Dc-eNL5On

  LV Write Access        read/write

  LV Status              available

  # open                 2

  LV Size                248.99 GB

  Current LE             63742

  Segments               1

  Allocation             inherit

  Read ahead sectors     0

  Block device           253:0

  --- Physical volumes ---

  PV Name               /dev/sddlmag1

  PV UUID               kkzkQD-uxqX-Sgp1-bS0j-jWhq-AoI0-kASm6O

  PV Status             allocatable

  Total PE / Free PE    63742 / 0

What the heck is /dev/sddlmag1  (that is SDDLmag1)?  I have all my FC
mounted as /dev/SDDLxxxx and I can't map that to any of the below:

ls -la /dev/sddlmag1

brw-r----- 1 root disk 251, 97 Mar 21 09:31 /dev/sddlmag1

I know by the size of the various LVM Volume Groups and by fdisk -l
/dev/sdX that there is a one to one correlation between sddlxxxx and
/dev/sdx, but except for one drive(FC mount) there are multiple choices
based on size.

/dev/disk # ls -la by-id/

total 0

drwxr-xr-x 2 root root 400 Mar 21 09:31 .

drwxr-xr-x 5 root root 100 Mar 21 09:31 ..

lrwxrwxrwx 1 root root  16 Mar 21 09:31
cciss-3600508b10010343956584f3134380001 -> ../../cciss/c0d0

lrwxrwxrwx 1 root root  18 Mar 21 09:31
cciss-3600508b10010343956584f3134380001-part1 -> ../../cciss/c0d0p1

lrwxrwxrwx 1 root root  18 Mar 21 09:31
cciss-3600508b10010343956584f3134380001-part2 -> ../../cciss/c0d0p2

lrwxrwxrwx 1 root root  18 Mar 21 09:31
cciss-3600508b10010343956584f3134380001-part3 -> ../../cciss/c0d0p3

lrwxrwxrwx 1 root root   9 Mar 21 09:31 scsi-1HITACHI_770131020049 ->
../../sdb

lrwxrwxrwx 1 root root  10 Mar 21 09:31 scsi-1HITACHI_770131020049-part1
-> ../../sdb1

lrwxrwxrwx 1 root root   9 Mar 21 09:31 scsi-1HITACHI_770131020050 ->
../../sda

lrwxrwxrwx 1 root root  10 Mar 21 09:31 scsi-1HITACHI_770131020050-part1
-> ../../sda1

lrwxrwxrwx 1 root root   9 Mar 21 09:31 scsi-1HITACHI_770131020051 ->
../../sdc

lrwxrwxrwx 1 root root  10 Mar 21 09:31 scsi-1HITACHI_770131020051-part1
-> ../../sdc1

lrwxrwxrwx 1 root root   9 Mar 21 09:31 scsi-1HITACHI_770131020091 ->
../../sdd

lrwxrwxrwx 1 root root  10 Mar 21 09:31 scsi-1HITACHI_770131020091-part1
-> ../../sdd1

lrwxrwxrwx 1 root root   9 Mar 21 09:31 scsi-1HITACHI_770131020126 ->
../../sde

lrwxrwxrwx 1 root root  10 Mar 21 09:31 scsi-1HITACHI_770131020126-part1
-> ../../sde1

lrwxrwxrwx 1 root root   9 Mar 21 09:31 scsi-1HITACHI_770131020127 ->
../../sdf

lrwxrwxrwx 1 root root  10 Mar 21 09:31 scsi-1HITACHI_770131020127-part1
-> ../../sdf1

lrwxrwxrwx 1 root root   9 Mar 21 09:31 scsi-1HITACHI_770131020128 ->
../../sdg

lrwxrwxrwx 1 root root  10 Mar 21 09:31 scsi-1HITACHI_770131020128-part1
-> ../../sdg1

/dev/disk # ls -la by-path/

total 0

drwxr-xr-x 2 root root 400 Mar 21 09:31 .

drwxr-xr-x 5 root root 100 Mar 21 09:31 ..

lrwxrwxrwx 1 root root  16 Mar 21 09:31
pci-0000:0b:08.0-cciss-0:40000000 -> ../../cciss/c0d0

lrwxrwxrwx 1 root root  18 Mar 21 09:31
pci-0000:0b:08.0-cciss-0:40000000-part1 -> ../../cciss/c0d0p1

lrwxrwxrwx 1 root root  18 Mar 21 09:31
pci-0000:0b:08.0-cciss-0:40000000-part2 -> ../../cciss/c0d0p2

lrwxrwxrwx 1 root root  18 Mar 21 09:31
pci-0000:0b:08.0-cciss-0:40000000-part3 -> ../../cciss/c0d0p3

lrwxrwxrwx 1 root root   9 Mar 21 09:31 pci-0000:16:00.0-scsi-0:0:0:0 ->
../../sda

lrwxrwxrwx 1 root root  10 Mar 21 09:31
pci-0000:16:00.0-scsi-0:0:0:0-part1 -> ../../sda1

lrwxrwxrwx 1 root root   9 Mar 21 09:31 pci-0000:16:00.0-scsi-0:0:0:1 ->
../../sdb

lrwxrwxrwx 1 root root  10 Mar 21 09:31
pci-0000:16:00.0-scsi-0:0:0:1-part1 -> ../../sdb1

lrwxrwxrwx 1 root root   9 Mar 21 09:31 pci-0000:16:00.0-scsi-0:0:0:2 ->
../../sdc

lrwxrwxrwx 1 root root  10 Mar 21 09:31
pci-0000:16:00.0-scsi-0:0:0:2-part1 -> ../../sdc1

lrwxrwxrwx 1 root root   9 Mar 21 09:31 pci-0000:16:00.0-scsi-0:0:0:3 ->
../../sdd

lrwxrwxrwx 1 root root  10 Mar 21 09:31
pci-0000:16:00.0-scsi-0:0:0:3-part1 -> ../../sdd1

lrwxrwxrwx 1 root root   9 Mar 21 09:31 pci-0000:16:00.0-scsi-0:0:0:4 ->
../../sde

lrwxrwxrwx 1 root root  10 Mar 21 09:31
pci-0000:16:00.0-scsi-0:0:0:4-part1 -> ../../sde1

lrwxrwxrwx 1 root root   9 Mar 21 09:31 pci-0000:16:00.0-scsi-0:0:0:5 ->
../../sdf

lrwxrwxrwx 1 root root  10 Mar 21 09:31
pci-0000:16:00.0-scsi-0:0:0:5-part1 -> ../../sdf1

lrwxrwxrwx 1 root root   9 Mar 21 09:31 pci-0000:16:00.0-scsi-0:0:0:6 ->
../../sdg

lrwxrwxrwx 1 root root  10 Mar 21 09:31
pci-0000:16:00.0-scsi-0:0:0:6-part1 -> ../../sdg1

ls -la by-uuid/

total 0

drwxr-xr-x 2 root root 600 Mar 21 09:31 .

drwxr-xr-x 5 root root 100 Mar 21 09:31 ..

lrwxrwxrwx 1 root root  10 Mar 21 09:31
13026f96-7d44-4509-aa94-35395448e110 -> ../../dm-2  

etc etc listing all the LVM logical volumes 

So, while to migrate off of Suse, I only need the max. amount of storage
each box is using, it is driving me up the wall that I can't say
/dev/SDDLmag1 ==/dev/sda or that /dev/sdb is used by VG foo and has lv
bar on it.

You all gave me such good advice on how to start mapping the info so I
could set up a target server to migrate to, I figured I would bounce
this off of the list.  Most of the employees here are Unix so they don't
know Linux dev mappings (which is why they hired me, but I have not
worked with FC).

Please include me in the reply so I can read them at work.

 Sincerely,

Damon Chesser

damon at damtek.com

________________________________

Disclaimer: This electronic transmission and any attachments contain
confidential information belonging to the sender. This information may
be legally protected. The information is intended only for the use of
the individual or entity named above. If you are not the intended
recipient or receive this message in error, you are hereby notified that
any disclosure, copying, distribution or taking of any action in
reliance on or regarding the contents of this information is strictly
prohibited. Please notify the sender immediately if you have received
this information in error.

www.acsi2000.com

Proud partner. Susan G. Komen for the Cure.

Please consider our environment before printing this e-mail or attachments.
----------------------------------
CONFIDENTIALITY NOTICE: This e-mail may contain privileged or confidential information and is for the sole use of the intended recipient(s). If you are not the intended recipient, any disclosure, copying, distribution, or use of the contents of this information is prohibited and may be unlawful. If you have received this electronic transmission in error, please reply immediately to the sender that you have received the message in error, and delete it. Thank you.
----------------------------------
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://mail.ale.org/pipermail/ale/attachments/20110419/212e0342/attachment-0001.html 