[prev in list] [next in list] [prev in thread] [next in thread] 

List:       openais
Subject:    Re: [Openais] Corosync: Coroipc freeze and segfaults on corosync
From:       Jan Friesse <jfriesse () redhat ! com>
Date:       2010-01-27 15:12:19
Message-ID: 4B6057D3.4070903 () redhat ! com
[Download RAW message or body]

Andrew,
definitively not -b, this will use image as base image and created image
as something to save only changes. I would recommend to use something like:
qemu-img convert -c -f raw -O qcow2 source dest.qcow

Regards,
  Honza

Andrew Beekhof wrote:
> On Wed, Jan 27, 2010 at 2:29 PM, Jan Friesse <jfriesse@redhat.com> wrote:
>> Andrew,
>> Trunk is definitively usable. But one problem is, that shutdown can end
>> with segfault.
> 
> Which doesn't really help test this :-(
> 
>> qemu-img should be able to create qcow2 compressed image from LVM.
> 
> Before I send across huge images, does this look right?
> 
> # qemu-img create -b /dev/System/pcmk-1 qcow2 pcmk-1.qcow2
> 
> Where
> 
>   LV Name                /dev/System/pcmk-1
>   VG Name                System
>   LV UUID                RC3wZT-YcWY-b8vo-d57L-im93-Q9na-OBkuQL
>   LV Write Access        read/write
>   LV snapshot status     active destination for /dev/System/pcmk-0
>   LV Status              available
> 
>> Regards,
>>  Honza
>>
>> Andrew Beekhof wrote:
>>> On Jan 27, 2010, at 2:12 PM, Jan Friesse wrote:
>>>
>>>> Andrew,
>>>> this is definitively bad and shouldn't ever happened (correct corosync
>>>> shutdown ends with Corosync Cluster Engine exiting with status -1 at
>>>> main.c:162). Sadly, I'm not able to reproduce what you describe on one
>>>> node with:
>>>> - Fedora12
>>>> - pacemaker from Fedora repository (no configuration, just added service
>>>> to corosync)
>>>> - Corosync trunk + my patch
>>>>
>>>> Can you please send my your configuration of Pacemaker (or better full
>>>> configuration of what you are using).
>>> Attached.
>>>
>>>
>>>
>>> ------------------------------------------------------------------------
>>>
>>>
>>>
>>>
>>> ------------------------------------------------------------------------
>>>
>>>
>>>
>>>
>>>> Or even better, do you think it is
>>>> possible to store somewhere VM (ideally compressed qcow2) with your
>>>> installation?
>>> I'm using lvm snapshots which probably aren't as conducive to transport.
>>>
>>> Before we go down that path though, is trunk usable without your patch?
>>> It may be that the logging behavior is an unrelated issue with trunk.
>>>
>>>
>>>
>>>> Regards,
>>>>  Honza
>>>>
>>>> Andrew Beekhof wrote:
>>>>> On Wed, Jan 27, 2010 at 8:45 AM, Andrew Beekhof <andrew@beekhof.net> wrote:
>>>>>> On Mon, Jan 25, 2010 at 4:12 PM, Jan Friesse <jfriesse@redhat.com> wrote:
>>>>>>> Andrew Beekhof wrote:
>>>>>>>> Can you describe what it does please.
>>>>>>>>
>>>>>>> Should ensure, that:
>>>>>>> - Service exit_fn is called before exit
>>>>>>> - all IPC using service is disconnected and wait to proper end of IPC thread
>>>>>>> -  service is correctly unlinked
>>>>>>>
>>>>>>> But what I think that Steve wants is to test, if pacemaker works
>>>>>>> correctly with this patch.
>>>>>> Yeah, but it helps to know what one is testing in order to know how
>>>>>> best to test it.
>>>>>> Running with trunk + your new patch now...
>>>>> Should logging be affected?
>>>>> I'm frequently seeing nothing at all from corosync after
>>>>>
>>>>> Jan 27 12:56:04 pcmk-4 corosync[1878]:   [pcmk  ] notice:
>>>>> pcmk_shutdown: Shutdown complete
>>>>> Jan 27 12:56:04 pcmk-4 corosync[1878]:   [SERV  ] Service engine
>>>>> unloaded: Pacemaker Cluster Manager 1.1.0
>>>>>
>>>>> There's no cores (ulimit -c is set to unlimited) and the processes are
>>>>> gone, so its unclear if there is a problem.
>>> -- Andrew
>>>
>>>
>>>
>>

_______________________________________________
Openais mailing list
Openais@lists.linux-foundation.org
https://lists.linux-foundation.org/mailman/listinfo/openais
[prev in list] [next in list] [prev in thread] [next in thread]