From: AJ Lewis <alewis@redhat.com>
To: Ming Zhang <mingz@ele.uri.edu>
Cc: LVM general discussion and development <linux-lvm@redhat.com>
Subject: Re: [linux-lvm] how to access the partition on LV?
Date: Thu, 28 Jul 2005 12:32:18 -0500 [thread overview]
Message-ID: <20050728173218.GH4954@null.msp.redhat.com> (raw)
In-Reply-To: <1122570830.9888.10.camel@localhost.localdomain>
[-- Attachment #1: Type: text/plain, Size: 2380 bytes --]
On Thu, Jul 28, 2005 at 01:13:50PM -0400, Ming Zhang wrote:
> On Thu, 2005-07-28 at 11:45 -0500, AJ Lewis wrote:
> > On Thu, Jul 28, 2005 at 11:17:41AM -0400, Ming Zhang wrote:
> > > I think this is a very common question but i can not find the answer.
> > > any idea on how to access the partition on these lv since no device
> > > node?
> > >
> > >
> > > [root@fc3-i386-2 ~]# fdisk /dev/vg1/v1 -l
> > >
> > > Disk /dev/vg1/v1: 469 MB, 469762048 bytes
> > > 255 heads, 63 sectors/track, 57 cylinders
> > > Units = cylinders of 16065 * 512 = 8225280 bytes
> > >
> > > Device Boot Start End Blocks Id System
> > > /dev/vg1/v1p1 1 13 104391 83 Linux
> > > /dev/vg1/v1p2 14 57 353430 83 Linux
> >
>
> the problem is that we export a LV via iscsi to a remote box and become
> a scsi disk. so it is partitioned and utilized. then it does have
> partition on it. even it is exported to a linux box, u possibly will
> use /dev/sdx1 instead of directly use /dev/sdx, rite?
Ahh - I see. Well, on the node exporting the LVs, you don't access it. I
dunno if kpartx or some other partitioning tool could do it - it might. But
as far as the standard partion handling code goes, LVs don't exist. I know
why you're doing it this way - I don't know why you want to access the
partitions on the exporting (target) node. Do you really need to?
> > You don't. Don't put partition tables on LVs. The whole point of using
> > LVM is you don't need to partition anymore, and your block devices can be
> > dynamic. If you another block devices, you lvcreate it. If you don't
> > have enough space in your VG, you add a PV to it, then lvcreate the new
> > block device. Have you read through the HOWTO referenced below?
>
> i can not see this HOWTO, where u referenced it?
It's at the bottom of all messages that go to the linux-lvm ML -
http://tldp.org/HOWTO/LVM-HOWTO/
--
AJ Lewis Voice: 612-638-0500
Red Hat E-Mail: alewis@redhat.com
One Main Street SE, Suite 209
Minneapolis, MN 55414
Current GPG fingerprint = D9F8 EDCE 4242 855F A03D 9B63 F50C 54A8 578C 8715
Grab the key at: http://people.redhat.com/alewis/gpg.html or one of the
many keyservers out there...
[-- Attachment #2: Type: application/pgp-signature, Size: 189 bytes --]
next prev parent reply other threads:[~2005-07-28 17:32 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-07-28 15:17 [linux-lvm] how to access the partition on LV? Ming Zhang
2005-07-28 16:45 ` AJ Lewis
2005-07-28 17:13 ` Ming Zhang
2005-07-28 17:32 ` AJ Lewis [this message]
2005-07-28 17:42 ` Ming Zhang
2005-07-28 18:03 ` AJ Lewis
2005-07-28 18:14 ` Ming Zhang
2005-07-29 20:56 ` Alasdair G Kergon
2005-07-29 21:14 ` Ming Zhang
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=20050728173218.GH4954@null.msp.redhat.com \
--to=alewis@redhat.com \
--cc=linux-lvm@redhat.com \
--cc=mingz@ele.uri.edu \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).