Re: [Xen-users] Xen cLVM and iSCSI

[Barry van Someren <barry@xxxxxxxxxxxxxxxx>]

Hey,

Thanks for that.
Actually clvm is less thorough as it only locks the LVM metadata and
not the actual access to the device.
My beef is not with clvm, it's good for what it does.
The problem is that I can't get the entire boatload of cluster extra's
that come with CentOS to work reliably (probably operator error)

I'm running tests on this right now and it's all looking good
especially since all the changes are done in 1 place and I've
implemented a queue to make sure that only 1 lvm command can be active
at any time.

Thank you for the suggestion.. I'm going to roll with it and see how it works.

Regards,

Barry

On Mon, May 4, 2009 at 4:30 PM, Javier Guerra <javier@xxxxxxxxxxx> wrote:
> On Sun, May 3, 2009 at 5:32 AM, Barry van Someren
> <barry@xxxxxxxxxxxxxxxx> wrote:
>> Basically what I intend to do:
>> -Have all the *.cfg's on a Rysnched folder
>> -Designate a master node from where all LVM actions are done
>> -One each LVM change, call a script on each slave to refresh the LVM 
>> metadata.
>
> to be a bit more on the safe side, check the dmsetup tool, especially
> do a `dmsetup suspend/resume` around the 'change/reload' process.
> even better, use some form of locks to make sure non-master nodes are
> io-suspended before doing the change... soon you'll have a full cLVM
> replacement.
>
>
> --
> Javier
>



-- 
Barry van Someren
---------------------------------------
LinkedIn: http://www.linkedin.com/in/barryvansomeren
Skype: BvsomerenSprout
Blog: http://blog.bvansomeren.com
KvK: 27317624
irc: BarryNL @ FreeNode

_______________________________________________
Xen-users mailing list
Xen-users@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-users