- Original Message -
> From: "Nicolas Ecarnot"
> To: "Federico Simoncelli"
> Cc: "users"
> Sent: Monday, February 17, 2014 10:14:56 AM
> Subject: Re: [Users] "Volume Group does not exist". Blame device-mapper ?
>
> Le 1
Le 14/02/2014 15:39, Federico Simoncelli a écrit :
Hi Nicolas,
are you still able to reproduce this issue? Are you using fedora or
centos?
If providing the logs is problematic for you could you try to ping me
on irc (fsimonce on #ovirt OFTC) so that we can work on the issue
together?
Thanks,
rom: "Nicolas Ecarnot"
> To: "users"
> Sent: Monday, January 20, 2014 11:06:21 AM
> Subject: [Users] "Volume Group does not exist". Blame device-mapper ?
>
> Hi,
>
> oVirt 3.3, no big issue since the recent snapshot joke, but all in all
> runni
Hi,
Please see inline response.
Regards,
Maor
On 01/29/2014 02:35 PM, Nicolas Ecarnot wrote:
> Le 29/01/2014 13:29, Maor Lipchuk a écrit :
>> Hi Nicolas,
>>
>> Can u please attach the VDSM logs of the problematic nodes and valid
>> nodes, the engine log and also the sanlock log.
>>
>> You wrote
Le 29/01/2014 13:36, Itamar Heim a écrit :
On 01/29/2014 02:35 PM, Nicolas Ecarnot wrote:
Le 29/01/2014 13:29, Maor Lipchuk a écrit :
Hi Nicolas,
Can u please attach the VDSM logs of the problematic nodes and valid
nodes, the engine log and also the sanlock log.
You wrote that many nodes sudd
On 01/29/2014 02:35 PM, Nicolas Ecarnot wrote:
Le 29/01/2014 13:29, Maor Lipchuk a écrit :
Hi Nicolas,
Can u please attach the VDSM logs of the problematic nodes and valid
nodes, the engine log and also the sanlock log.
You wrote that many nodes suddenly began to become
unresponsive,
Do you me
Le 29/01/2014 13:29, Maor Lipchuk a écrit :
Hi Nicolas,
Can u please attach the VDSM logs of the problematic nodes and valid
nodes, the engine log and also the sanlock log.
You wrote that many nodes suddenly began to become
unresponsive,
Do you mean that the hosts switched to non-responsive sta
Hi Nicolas,
Can u please attach the VDSM logs of the problematic nodes and valid
nodes, the engine log and also the sanlock log.
You wrote that many nodes suddenly began to become
unresponsive,
Do you mean that the hosts switched to non-responsive status in the engine?
I'm asking that because non
Le 26/01/2014 23:23, Itamar Heim a écrit :
On 01/20/2014 12:06 PM, Nicolas Ecarnot wrote:
Hi,
oVirt 3.3, no big issue since the recent snapshot joke, but all in all
running fine.
All my VM are stored in a iSCSI SAN. The VM usually are using only one
or two disks (1: system, 2: data) and it is
On 01/20/2014 12:06 PM, Nicolas Ecarnot wrote:
Hi,
oVirt 3.3, no big issue since the recent snapshot joke, but all in all
running fine.
All my VM are stored in a iSCSI SAN. The VM usually are using only one
or two disks (1: system, 2: data) and it is OK.
Friday, I created a new LUN. Inside a V
Hi,
oVirt 3.3, no big issue since the recent snapshot joke, but all in all
running fine.
All my VM are stored in a iSCSI SAN. The VM usually are using only one
or two disks (1: system, 2: data) and it is OK.
Friday, I created a new LUN. Inside a VM, I linked to it via iscsiadm
and successf
11 matches
Mail list logo
