Please check: https://bugzilla.redhat.com/show_bug.cgi?id=881941 which explains what actually the bug is. I might attach there the logs you request too.
I had to refer to the bug before but I just had forgotten about it. ----- Mensaje original ----- > De: "Yeela Kaplan" <[email protected]> > Para: "Adrian Gibanel" <[email protected]> > CC: [email protected] > Enviados: Lunes, 3 de Diciembre 2012 10:18:46 > Asunto: Re: [Users] Lvm vgs failed on allinone setup > Hi Adrian, > Your domain ('033a2b87-def7-4c27-ab74-9860531f2ed4') is probably NFS. > Don't worry about the failed vgs errors, it is not the problem. > Please attach the full vdsm and engine logs so we can detect why the > domain is set to > maintenance after reboot. > -- > Yeela > ----- Original Message ----- > > From: "Adrian Gibanel" <[email protected]> > > To: [email protected] > > Sent: Tuesday, November 27, 2012 6:53:50 PM > > Subject: Re: [Users] Lvm vgs failed on allinone setup > > > > I've debugged the lvm vgs failed part. It seems to run this > > command: > > > > [adrian@server ~]$ sudo vgs --noheadings --units b --nosuffix > > --separator \| -o > > uuid,name,attr,size,free,extent_size,extent_count,free_count,tags,vg_mda_size,vg_mda_free > > 033a2b87-def7-4c27-ab74-9860531f2ed4 > > Volume group "033a2b87-def7-4c27-ab74-9860531f2ed4" not found > > > > If I run the same commands without arguments I found out the > > current > > VGs: > > > > [adrian@server ~]$ sudo vgs --noheadings --units b --nosuffix > > --separator \| -o > > uuid,name,attr,size,free,extent_size,extent_count,free_count,tags,vg_mda_size,vg_mda_free > > Na9Bdu-aELy-1G3m-JgcV-dBYM-PfaP-arsvUo|maquinasVG|wz--n-|1989115117568|406419668992|4194304|474242|96898||1048064|522240 > > > > So I try to run it with the uuid seen: > > [adrian@server ~]$ sudo vgs --noheadings --units b --nosuffix > > --separator \| -o > > uuid,name,attr,size,free,extent_size,extent_count,free_count,tags,vg_mda_size,vg_mda_free > > Na9Bdu-aELy-1G3m-JgcV-dBYM-PfaP-arsvUo Volume group > > "Na9Bdu-aELy-1G3m-JgcV-dBYM-PfaP-arsvUo" not found > > it says it cannot find it. > > > > Now with the name: > > [adrian@server ~]$ sudo vgs --noheadings --units b --nosuffix > > --separator \| -o > > uuid,name,attr,size,free,extent_size,extent_count,free_count,tags,vg_mda_size,vg_mda_free > > maquinasVG > > Na9Bdu-aELy-1G3m-JgcV-dBYM-PfaP-arsvUo|maquinasVG|wz--n-|1989115117568|406419668992|4194304|474242|96898||1048064|522240 > > > > It works! > > > > So that would maybe fix it. Although I'm not very sure because this > > is just a WARNING. And because I think it's not a good idea to > > rename current uuids for storage or iso domains (not sure which > > it's > > exactly) in the database just to match the LVM uuids. > > > > Now I'm going to debug the other messages which are ERRORs and not > > warnings. > > > > ----- Mensaje original ----- > > > > > De: "Adrian Gibanel" <[email protected]> > > > Para: [email protected] > > > Enviados: Martes, 27 de Noviembre 2012 17:16:50 > > > Asunto: Re: [Users] Lvm vgs failed on allinone setup > > > > > After seeing that I had many named errors I've disabled ipv6 by > > > adding -4 to OPTIONS line as described in: > > > http://www.hafizonline.net/blog/?p=164 . After had I have > > > rebooted > > > the logs regarding lvm change a bit. Here you are: > > > > > Nov 27 17:09:15 server vdsm Storage.LVM WARNING lvm vgs failed: 5 > > > [] > > > [' Volume group "c20da291-baf5-480a-b314-b775a6dde6e8" not > > > found'] > > > > -- > > > > -- > > Adrián Gibanel -- Adrián Gibanel I.T. Manager +34 675 683 301 www.btactic.com Ens podeu seguir a/Nos podeis seguir en: i Abans d´imprimir aquest missatge, pensa en el medi ambient. El medi ambient és cosa de tothom. / Antes de imprimir el mensaje piensa en el medio ambiente. El medio ambiente es cosa de todos. AVIS: El contingut d'aquest missatge i els seus annexos és confidencial. Si no en sou el destinatari, us fem saber que està prohibit utilitzar-lo, divulgar-lo i/o copiar-lo sense tenir l'autorització corresponent. Si heu rebut aquest missatge per error, us agrairem que ho feu saber immediatament al remitent i que procediu a destruir el missatge . AVISO: El contenido de este mensaje y de sus anexos es confidencial. Si no es el destinatario, les hacemos saber que está prohibido utilizarlo, divulgarlo y/o copiarlo sin tener la autorización correspondiente. Si han recibido este mensaje por error, les agradeceríamos que lo hagan saber inmediatamente al remitente y que procedan a destruir el mensaje .
_______________________________________________ Users mailing list [email protected] http://lists.ovirt.org/mailman/listinfo/users
