[Date Prev][Date Next]   [Thread Prev][Thread Next]   [Thread Index] [Date Index] [Author Index]

Re: [linux-lvm] how to access the partition on LV?

On Thu, Jul 28, 2005 at 01:42:10PM -0400, Ming Zhang wrote:
> On Thu, 2005-07-28 at 12:32 -0500, AJ Lewis wrote:
> > On Thu, Jul 28, 2005 at 01:13:50PM -0400, Ming Zhang wrote:
> > > 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?
> yes, i guess that is the only solution. we have end users want that
> feature. so i think a work around is to run a iscsi initiator at local
> site and access via iscsi again.

Could play with loopback devices too if you need to do it on the target - that
might get nasty quickly though.
> > > 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/ 
> i guess this is because i got the email from u directly. so lvm list
> will not send to me again. and only email via it will have that link. i
> checked my archival and all emails via lvm list has that.

Heh - yep, that'd do it ;) 

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: pgp12dneXNFvh.pgp
Description: PGP signature

[Date Prev][Date Next]   [Thread Prev][Thread Next]   [Thread Index] [Date Index] [Author Index]