For the device in question, I did: "fdisk -l /dev/md10". I received the following output:
Disk /dev/md10: 73.2 GB, 73270689792 bytes
2 heads, 4 sectors/track, 17888352 cylinders
Units = cylinders of 8 * 512 = 4096 bytes
Disk /dev/md10 doesn't contain a valid partition table
However, when I list out /dev/mpath, I get the following:
lrwxrwxrwx 1 root root 7 Mar 26 07:28 mpath3 -> ../dm-8
lrwxrwxrwx 1 root root 8 Mar 26 07:28 mpath3p1 -> ../dm-10
lrwxrwxrwx 1 root root 7 Mar 26 07:28 mpath2p1 -> ../dm-9
lrwxrwxrwx 1 root root 7 Mar 26 07:28 mpath2 -> ../dm-7
How do I interpret this output? Does it mean the absence of "md10" means that it resides on the internal drive. I know that /dev/dm-9 and /dev/dm-10 reside on the SAN. But, I guess I was looking for a more concrete way to tie /dev/md10 to the attached devices in /proc/scsi/scsi so that I can definitely say it's on the FUJITSU drive or on the SUN StorEdge 3510.
From: linuxmails lists gmail com
To: linux-lvm redhat com
Date: Wed, 14 Apr 2010 00:36:37 -0500
Subject: Re: [linux-lvm] How do I tell what disk a volume group reside on
Assuming that you are using MPIO , have you compared the output of fdisk -l to the dm device names in /dev/mpath?
On Tue, 13 Apr 2010 20:59:40 -0400
Vickie Troy-McKoy <vtmckoy hotmail com> wrote:
I have a RedHat4 server connected to a SAN 3510 Array. On the host
server, there are two volume groups set up--root_vg and san_vg. I'm
assuming that root_vg resides on the internal disks and san_vg on the
SAN. But, how can I check to make sure this is the case?
The New Busy is not the old busy. Search, chat and e-mail from your inbox. Get started.