From: Ray Morris <support@bettercgi.com>
To: LVM general discussion and development <linux-lvm@redhat.com>
Subject: Re: [linux-lvm] How do I tell what disk a volume group reside on
Date: Wed, 14 Apr 2010 10:42:47 -0500 [thread overview]
Message-ID: <1271259767.9436.17@raydesk1.bettercgi.com> (raw)
In-Reply-To: <BAY110-W4728F879DCB6C9F915B971BE100@phx.gbl> (from vtmckoy@hotmail.com on Wed Apr 14 07:16:56 2010)
> however, I want to ensure that /dev/md10 [root_vg] resides
> on the internal disks. How can I ensure that?
Note that this is no longer an LVM question, but a
softraid question, and when the softraid question is answered
it leads you to a SAN question. Hat's because LVM doesn't
know or care where the md10 device is physically located, much
less know or care where any component devices are.
To see which devices make up
/dev/md10, do:
cat /proc/mdstat
Output will look something like :
Personalities : [raid6] [raid5] [raid4]
md10 : active raid5 sda2[0] sdc2[2] sdb2[1]
772370304 blocks level 5, 64k chunk, algorithm 2 [3/3] [UUU]
unused devices: <none>
The second line tells us that md10 is made up of these devices:
sda2[0] sdc2[2] sdb2[1]
Now the question becomes are those devices internal? If you
can't tell from the names, lsscsi might come in handy. If it's
still not apparent, you have a SAN question that depends on the
type of SAN you have. It's even possible to set up a SAS SAN with
internal and external storage attached to the same card. If the
"identify" lights aren't hooked up, the only way to know for sure
would be to compare serial numbers with the output of sdparm!
It may seem strange that it can be so "hard" to know what's
what, but that's exactly where the magic comes from - you can
make a RAID of external devices, internal devices, or a mix
precisely because the RAID system doesn't know or care where they
are physically located.
--
Ray Morris
support@bettercgi.com
Strongbox - The next generation in site security:
http://www.bettercgi.com/strongbox/
Throttlebox - Intelligent Bandwidth Control
http://www.bettercgi.com/throttlebox/
Strongbox / Throttlebox affiliate program:
http://www.bettercgi.com/affiliates/user/register.php
On 04/14/2010 07:16:56 AM, Vickie Troy-McKoy wrote:
>
>
> Thank you; but I've tried that command. It gives me the output
> below;
> however, I want to ensure that /dev/md10 [root_vg] resides on the
> internal
> disks. How can I ensure that?
>
>
> PV VG Fmt Attr PSize PFree
> /dev/dm-10 san_vg lvm2 a- 299.99G 0
> /dev/dm-9 san_vg lvm2 a- 174.99G 0
> /dev/md10 root_vg lvm2 a- 68.22G 12.44G
>
> Regards,
next prev parent reply other threads:[~2010-04-14 15:39 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-04-14 0:59 [linux-lvm] How do I tell what disk a volume group reside on Vickie Troy-McKoy
2010-04-14 2:28 ` Phillip Susi
2010-04-14 2:43 ` [linux-lvm] nevermind Phillip Susi
2010-04-14 5:36 ` [linux-lvm] How do I tell what disk a volume group reside on linuxmails.lists
2010-04-14 12:34 ` Vickie Troy-McKoy
2010-04-14 5:21 ` Luca Berra
2010-04-14 8:47 ` brem belguebli
2010-04-14 12:16 ` Vickie Troy-McKoy
2010-04-14 15:42 ` Ray Morris [this message]
2010-04-14 13:23 ` Ron Johnson
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1271259767.9436.17@raydesk1.bettercgi.com \
--to=support@bettercgi.com \
--cc=linux-lvm@redhat.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.