What a nightmare! Hitachi is being bought by Seagate so maybe that crappy design will hit the bit bucket.<br><br><div class="gmail_quote">On Tue, Apr 19, 2011 at 6:48 PM, Greg Freemyer <span dir="ltr"><<a href="mailto:greg.freemyer@gmail.com">greg.freemyer@gmail.com</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin: 0pt 0pt 0pt 0.8ex; border-left: 1px solid rgb(204, 204, 204); padding-left: 1ex;">Damon,<br>
<br>
Hitachi is weird mainframe storage. It has weird workarounds that<br>
won't apply to your new SAN. Your new SAN should be able to export<br>
the whole /dev/sddlmag1 sized logical volume, as a single volume. So<br>
you really don't care how it came to be in a Hitachi world.<br>
<br>
== but maybe this will help you satisfy your curiosity<br>
<br>
you saw these links in your output, right?<br>
<br>
scsi-1HITACHI_770131020049 -> ../../sdb<br>
scsi-1HITACHI_770131020050 -> ../../sda<br>
scsi-1HITACHI_770131020051 -> ../../sdc<br>
scsi-1HITACHI_770131020091 -> ../../sdd<br>
scsi-1HITACHI_770131020126 -> ../../sde<br>
scsi-1HITACHI_770131020127 -> ../../sdf<br>
scsi-1HITACHI_770131020128 -> ../../sdg<br>
<br>
So that I believe is your 7 volumes as exported by Hitachi.<br>
<br>
It has been a while, but if I recall correctly, the Hitachi hardware<br>
can only export relatively small volumes. So each of the above I<br>
suspect is small. Maybe 64GB each?<br>
<br>
(My memory is actually 4GB max per Hitachi volume, but I don't trust<br>
that memory.)<br>
<br>
Hitachi then provided their own proprietary LVM like software to merge<br>
all the above together. The reason being they wanted the same CLI<br>
tools to work in various UNIX/Linux environment.<br>
<br>
If one of your co-workers is a Hitachi storage person, they can<br>
probably tell you what tools are used to see how the 7 volumes are<br>
combined into one.<br>
<br>
Then it looks like LVM is layered on top to break it back apart.<br>
<br>
It may sound crazy, but if I recall right, a large Hitachi setup could<br>
have literally hundreds of exported volumes, so trusting native volume<br>
management tools to work was not a good idea.<br>
<br>
<br>
Greg<br>
<div><div></div><div class="h5"><br>
On Tue, Apr 19, 2011 at 12:03 PM, Damon Chesser <<a href="mailto:dchesser@acsi2000.com">dchesser@acsi2000.com</a>> wrote:<br>
> Here is my problem: I have 7 mount that are from FC on a hitatchi. Suse<br>
> 10.2 on a HP server (6 series?) with two qlogic cards.<br>
><br>
><br>
><br>
> I have one phys. Drive presented on the server /dev/ccsis/c0d0<br>
><br>
><br>
><br>
> LVM is in use, everything is mounted as a LV except for /boot and /root on<br>
> c0d0 (c0d0p1, c0d0p2)<br>
><br>
><br>
><br>
> I can run vgdisplay –v FOO and find out what “drive” FOO is mounted on: in<br>
> part:<br>
><br>
><br>
><br>
> --- Logical volume ---<br>
><br>
> LV Name /dev/FOO/FOO<br>
><br>
> VG Name FOO<br>
><br>
> LV UUID ZC0ZlW-UK4r-TC6j-Yvj2-qf7Y-34Dc-eNL5On<br>
><br>
> LV Write Access read/write<br>
><br>
> LV Status available<br>
><br>
> # open 2<br>
><br>
> LV Size 248.99 GB<br>
><br>
> Current LE 63742<br>
><br>
> Segments 1<br>
><br>
> Allocation inherit<br>
><br>
> Read ahead sectors 0<br>
><br>
> Block device 253:0<br>
><br>
><br>
><br>
> --- Physical volumes ---<br>
><br>
> PV Name /dev/sddlmag1<br>
><br>
> PV UUID kkzkQD-uxqX-Sgp1-bS0j-jWhq-AoI0-kASm6O<br>
><br>
> PV Status allocatable<br>
><br>
> Total PE / Free PE 63742 / 0<br>
><br>
><br>
><br>
> What the heck is /dev/sddlmag1 (that is SDDLmag1)? I have all my FC<br>
> mounted as /dev/SDDLxxxx and I can’t map that to any of the below:<br>
><br>
><br>
><br>
><br>
><br>
> ls -la /dev/sddlmag1<br>
><br>
> brw-r----- 1 root disk 251, 97 Mar 21 09:31 /dev/sddlmag1<br>
><br>
><br>
><br>
> I know by the size of the various LVM Volume Groups and by fdisk –l /dev/sdX<br>
> that there is a one to one correlation between sddlxxxx and /dev/sdx, but<br>
> except for one drive(FC mount) there are multiple choices based on size.<br>
><br>
><br>
><br>
><br>
><br>
><br>
><br>
><br>
><br>
><br>
><br>
> /dev/disk # ls -la by-id/<br>
><br>
> total 0<br>
><br>
> drwxr-xr-x 2 root root 400 Mar 21 09:31 .<br>
><br>
> drwxr-xr-x 5 root root 100 Mar 21 09:31 ..<br>
><br>
> lrwxrwxrwx 1 root root 16 Mar 21 09:31<br>
> cciss-3600508b10010343956584f3134380001 -> ../../cciss/c0d0<br>
><br>
> lrwxrwxrwx 1 root root 18 Mar 21 09:31<br>
> cciss-3600508b10010343956584f3134380001-part1 -> ../../cciss/c0d0p1<br>
><br>
> lrwxrwxrwx 1 root root 18 Mar 21 09:31<br>
> cciss-3600508b10010343956584f3134380001-part2 -> ../../cciss/c0d0p2<br>
><br>
> lrwxrwxrwx 1 root root 18 Mar 21 09:31<br>
> cciss-3600508b10010343956584f3134380001-part3 -> ../../cciss/c0d0p3<br>
><br>
> lrwxrwxrwx 1 root root 9 Mar 21 09:31 scsi-1HITACHI_770131020049 -><br>
> ../../sdb<br>
><br>
> lrwxrwxrwx 1 root root 10 Mar 21 09:31 scsi-1HITACHI_770131020049-part1 -><br>
> ../../sdb1<br>
><br>
> lrwxrwxrwx 1 root root 9 Mar 21 09:31 scsi-1HITACHI_770131020050 -><br>
> ../../sda<br>
><br>
> lrwxrwxrwx 1 root root 10 Mar 21 09:31 scsi-1HITACHI_770131020050-part1 -><br>
> ../../sda1<br>
><br>
> lrwxrwxrwx 1 root root 9 Mar 21 09:31 scsi-1HITACHI_770131020051 -><br>
> ../../sdc<br>
><br>
> lrwxrwxrwx 1 root root 10 Mar 21 09:31 scsi-1HITACHI_770131020051-part1 -><br>
> ../../sdc1<br>
><br>
> lrwxrwxrwx 1 root root 9 Mar 21 09:31 scsi-1HITACHI_770131020091 -><br>
> ../../sdd<br>
><br>
> lrwxrwxrwx 1 root root 10 Mar 21 09:31 scsi-1HITACHI_770131020091-part1 -><br>
> ../../sdd1<br>
><br>
> lrwxrwxrwx 1 root root 9 Mar 21 09:31 scsi-1HITACHI_770131020126 -><br>
> ../../sde<br>
><br>
> lrwxrwxrwx 1 root root 10 Mar 21 09:31 scsi-1HITACHI_770131020126-part1 -><br>
> ../../sde1<br>
><br>
> lrwxrwxrwx 1 root root 9 Mar 21 09:31 scsi-1HITACHI_770131020127 -><br>
> ../../sdf<br>
><br>
> lrwxrwxrwx 1 root root 10 Mar 21 09:31 scsi-1HITACHI_770131020127-part1 -><br>
> ../../sdf1<br>
><br>
> lrwxrwxrwx 1 root root 9 Mar 21 09:31 scsi-1HITACHI_770131020128 -><br>
> ../../sdg<br>
><br>
> lrwxrwxrwx 1 root root 10 Mar 21 09:31 scsi-1HITACHI_770131020128-part1 -><br>
> ../../sdg1<br>
><br>
><br>
><br>
> /dev/disk # ls -la by-path/<br>
><br>
> total 0<br>
><br>
> drwxr-xr-x 2 root root 400 Mar 21 09:31 .<br>
><br>
> drwxr-xr-x 5 root root 100 Mar 21 09:31 ..<br>
><br>
> lrwxrwxrwx 1 root root 16 Mar 21 09:31 pci-0000:0b:08.0-cciss-0:40000000 -><br>
> ../../cciss/c0d0<br>
><br>
> lrwxrwxrwx 1 root root 18 Mar 21 09:31<br>
> pci-0000:0b:08.0-cciss-0:40000000-part1 -> ../../cciss/c0d0p1<br>
><br>
> lrwxrwxrwx 1 root root 18 Mar 21 09:31<br>
> pci-0000:0b:08.0-cciss-0:40000000-part2 -> ../../cciss/c0d0p2<br>
><br>
> lrwxrwxrwx 1 root root 18 Mar 21 09:31<br>
> pci-0000:0b:08.0-cciss-0:40000000-part3 -> ../../cciss/c0d0p3<br>
><br>
> lrwxrwxrwx 1 root root 9 Mar 21 09:31 pci-0000:16:00.0-scsi-0:0:0:0 -><br>
> ../../sda<br>
><br>
> lrwxrwxrwx 1 root root 10 Mar 21 09:31 pci-0000:16:00.0-scsi-0:0:0:0-part1<br>
> -> ../../sda1<br>
><br>
> lrwxrwxrwx 1 root root 9 Mar 21 09:31 pci-0000:16:00.0-scsi-0:0:0:1 -><br>
> ../../sdb<br>
><br>
> lrwxrwxrwx 1 root root 10 Mar 21 09:31 pci-0000:16:00.0-scsi-0:0:0:1-part1<br>
> -> ../../sdb1<br>
><br>
> lrwxrwxrwx 1 root root 9 Mar 21 09:31 pci-0000:16:00.0-scsi-0:0:0:2 -><br>
> ../../sdc<br>
><br>
> lrwxrwxrwx 1 root root 10 Mar 21 09:31 pci-0000:16:00.0-scsi-0:0:0:2-part1<br>
> -> ../../sdc1<br>
><br>
> lrwxrwxrwx 1 root root 9 Mar 21 09:31 pci-0000:16:00.0-scsi-0:0:0:3 -><br>
> ../../sdd<br>
><br>
> lrwxrwxrwx 1 root root 10 Mar 21 09:31 pci-0000:16:00.0-scsi-0:0:0:3-part1<br>
> -> ../../sdd1<br>
><br>
> lrwxrwxrwx 1 root root 9 Mar 21 09:31 pci-0000:16:00.0-scsi-0:0:0:4 -><br>
> ../../sde<br>
><br>
> lrwxrwxrwx 1 root root 10 Mar 21 09:31 pci-0000:16:00.0-scsi-0:0:0:4-part1<br>
> -> ../../sde1<br>
><br>
> lrwxrwxrwx 1 root root 9 Mar 21 09:31 pci-0000:16:00.0-scsi-0:0:0:5 -><br>
> ../../sdf<br>
><br>
> lrwxrwxrwx 1 root root 10 Mar 21 09:31 pci-0000:16:00.0-scsi-0:0:0:5-part1<br>
> -> ../../sdf1<br>
><br>
> lrwxrwxrwx 1 root root 9 Mar 21 09:31 pci-0000:16:00.0-scsi-0:0:0:6 -><br>
> ../../sdg<br>
><br>
> lrwxrwxrwx 1 root root 10 Mar 21 09:31 pci-0000:16:00.0-scsi-0:0:0:6-part1<br>
> -> ../../sdg1<br>
><br>
><br>
><br>
><br>
><br>
> ls -la by-uuid/<br>
><br>
> total 0<br>
><br>
> drwxr-xr-x 2 root root 600 Mar 21 09:31 .<br>
><br>
> drwxr-xr-x 5 root root 100 Mar 21 09:31 ..<br>
><br>
> lrwxrwxrwx 1 root root 10 Mar 21 09:31 13026f96-7d44-4509-aa94-35395448e110<br>
> -> ../../dm-2<br>
><br>
> etc etc listing all the LVM logical volumes<br>
><br>
><br>
><br>
><br>
><br>
> So, while to migrate off of Suse, I only need the max. amount of storage<br>
> each box is using, it is driving me up the wall that I can’t say<br>
> /dev/SDDLmag1 ==/dev/sda or that /dev/sdb is used by VG foo and has lv bar<br>
> on it.<br>
><br>
><br>
><br>
> You all gave me such good advice on how to start mapping the info so I could<br>
> set up a target server to migrate to, I figured I would bounce this off of<br>
> the list. Most of the employees here are Unix so they don’t know Linux dev<br>
> mappings (which is why they hired me, but I have not worked with FC).<br>
><br>
><br>
><br>
> Please include me in the reply so I can read them at work.<br>
><br>
><br>
><br>
> Sincerely,<br>
><br>
><br>
><br>
> Damon Chesser<br>
><br>
> <a href="mailto:damon@damtek.com">damon@damtek.com</a><br>
><br>
><br>
><br>
><br>
><br>
> ________________________________<br>
> Disclaimer: This electronic transmission and any attachments contain<br>
> confidential information belonging to the sender. This information may be<br>
> legally protected. The information is intended only for the use of the<br>
> individual or entity named above. If you are not the intended recipient or<br>
> receive this message in error, you are hereby notified that any disclosure,<br>
> copying, distribution or taking of any action in reliance on or regarding<br>
> the contents of this information is strictly prohibited. Please notify the<br>
> sender immediately if you have received this information in error.<br>
><br>
> <a href="http://www.acsi2000.com" target="_blank">www.acsi2000.com</a><br>
><br>
</div></div>> _______________________________________________<br>
> Ale mailing list<br>
> <a href="mailto:Ale@ale.org">Ale@ale.org</a><br>
> <a href="http://mail.ale.org/mailman/listinfo/ale" target="_blank">http://mail.ale.org/mailman/listinfo/ale</a><br>
> See JOBS, ANNOUNCE and SCHOOLS lists at<br>
> <a href="http://mail.ale.org/mailman/listinfo" target="_blank">http://mail.ale.org/mailman/listinfo</a><br>
><br>
><br>
<br>
<br>
<br>
--<br>
Greg Freemyer<br>
Head of EDD Tape Extraction and Processing team<br>
Litigation Triage Solutions Specialist<br>
<a href="http://www.linkedin.com/in/gregfreemyer" target="_blank">http://www.linkedin.com/in/gregfreemyer</a><br>
CNN/TruTV Aired Forensic Imaging Demo -<br>
<a href="http://insession.blogs.cnn.com/2010/03/23/how-computer-evidence-gets-retrieved/" target="_blank">http://insession.blogs.cnn.com/2010/03/23/how-computer-evidence-gets-retrieved/</a><br>
<br>
The Norcross Group<br>
The Intersection of Evidence & Technology<br>
<a href="http://www.norcrossgroup.com" target="_blank">http://www.norcrossgroup.com</a><br>
<br>
_______________________________________________<br>
Ale mailing list<br>
<a href="mailto:Ale@ale.org">Ale@ale.org</a><br>
<a href="http://mail.ale.org/mailman/listinfo/ale" target="_blank">http://mail.ale.org/mailman/listinfo/ale</a><br>
See JOBS, ANNOUNCE and SCHOOLS lists at<br>
<a href="http://mail.ale.org/mailman/listinfo" target="_blank">http://mail.ale.org/mailman/listinfo</a><br>
</blockquote></div><br><br clear="all"><br>-- <br>-- <br>James P. Kinney III<br>I would rather stumble along in freedom than walk effortlessly in chains.<br><br><br>