Estamos teniendo un problema con el almacenamiento asociados a nuestros ESxi 5.1.
Hemos instalado dos nuevos servidores pero al asociarles los volúmenes, nos los reconoce como SNAPSHOT.
Al reiniciar otraos servidores que antes funcionaban, ahora nos pasa lo mismo.
Al ejecutar: esxcli storage vmfs snapshot list , nos aparecen los volúmenes
512bd47c-7f1625dc-4518-0010188e5e7c
Volume Name: VMSERVERS
VMFS UUID: 512bd47c-7f1625dc-4518-0010188e5e7c
Can mount: true
Reason for un-mountability:
Can resignature: true
Reason for non-resignaturability:
Unresolved Extent Count: 1
51c36c5b-4cd02cc5-3579-0010188e5e7c
Volume Name: VMVIEW
VMFS UUID: 51c36c5b-4cd02cc5-3579-0010188e5e7c
Can mount: true
Reason for un-mountability:
Can resignature: true
Reason for non-resignaturability:
Unresolved Extent Count: 1
51c37ada-a2bfbbc3-64ce-0010188e5e7c
Volume Name: VMVIEW2
VMFS UUID: 51c37ada-a2bfbbc3-64ce-0010188e5e7c
Can mount: true
Reason for un-mountability:
Can resignature: true
Reason for non-resignaturability:
Unresolved Extent Count: 1
He visto el comando para forzar la firma del volumen para montarlo;
#esxcli storage vmfs snapshot resignature -l "XXXX"
¿Se destruyen datos con este comando?
¿Es permanente este cambio?
¿Cuál sería el proceso para que resto montara estos volúmenes correctamente?
Muchas gracias
======
We are having a problem with the associated storage our ESXi 5.1.
We have installed two new servers but associating volumes , we recognize them as SNAPSHOT.
Restarting otraos servers that worked previously , we now feel the same.
When you run:
#esxcli storage snapshot vmfs list we published volumes
I have seen the command to force the signing of the volume to be mounted ;
#esxcli snapshot storage vmfs resignature -l "XXXX "
Are data destroyed with this command ?
Is this change permanent ?
What would be the process for other mount these volumes correctly?
Thank you very much
