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

Re: [linux-lvm] linux-lvm Digest, Vol 78, Issue 4



-----Original Message-----
From: linux-lvm-bounces redhat com [mailto:linux-lvm-bounces redhat com]
On Behalf Of brem belguebli
Sent: Wednesday, August 18, 2010 7:01 AM
To: LVM general discussion and development
Subject: Re: [linux-lvm] linux-lvm Digest, Vol 78, Issue 4

Hi

2010/8/18 Bryn M. Reeves <bmr redhat com>:
> On 08/17/2010 09:16 PM, Daksh Chauhan wrote:
>>> A little history and why I am asking the question in this list.
>>> The customer needed to move from an existing SAN to a new SAN and
wanted
>>> as little as possible down time for the Application. So they zoned
the
>>> new SAN for access by the system and then added the new LUNs to the
>>> existing Volume Group. Then ran the pvmove commands. It worked with
no
>>> problem on one of the PVs, but on the second one all the I/O hung at
the
>>> Application and any commands that access the LVM information such as
>>> vgdisplay.
>>
>> Why not use LVM mirroring? Checkout lvconvert...
>
> Wrong tool for the job. There's currently no way to "split" an LVM2
> mirror leaving two usable devices (without resorting to manual edits
of
> the metadata anyway).
>
Tricky but could work :
1) Add the target PV to the VG
2) lvconvert your linear LV to mirrored (each miror leg on each PV)
once synchronization is done
3) lvconvert the mirored LV to linear by removing the old PV (if
lvconvert allows you to do so).

> Using pvmove is the right way to approach this problem with the
current
> tools and since it's going to be using the same kernel infrastructure
to
> shovel the data around there's no guarantee the user won't run into
the
> same kind of problem.
>
> Regards,
> Bryn.

============
I am not sure who suggested using the lvconvert command, but just
completed trying it. It works without hanging, but it does impact the
performance of the Application because of the I/O to synchronize the new
mirror. It seem the synchronizing has a higher priority than all the
other I/O.

Is there any way to control the synchronizing to limit the impact to the
Application?

I have looked for options to the lvconvert command and did not find
anything that.

I guess I could try the nice command to see if it affects it at all.

Any help with this would be greatly appreciated.

-----
Jack Allen


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