Skip to main content
NetApp Knowledge Base

Search

  • Filter results by:
    • View attachments
    Searching in
    About 2 results
    • Openstack Cinder volume: VM with ERROR state Failed to get "write" lock\nIs another process using the image
      https://kb.netapp.com/Cloud/OpenStack/Openstack_Cinder_volume__VM_with_ERROR_state_Failed_to_get_write_lock_nIs_another_process_using_the_image
      which causes VM running on that compute to an ERROR state as the cinder-volume with the below error. 2022-09-06 14:07:08.378 7 ERROR oslo_messaging.rpc.server libvirt.libvirtError: internal error: qem...which causes VM running on that compute to an ERROR state as the cinder-volume with the below error. 2022-09-06 14:07:08.378 7 ERROR oslo_messaging.rpc.server libvirt.libvirtError: internal error: qemu unexpectedly closed the monitor: 2022-09-06T08:37:07.310519Z xxx-kvm: -device vir-xxx-pci,bus=pci.0,addr=0x4,drive=libvirt-1-format,id=virtio-disk0,bootindex=1,write-cache=on,serial=f0a03ccf-b923-4c73-a6a0-f57d4eb34db5: Failed to get shared "write" lock
    • Unix clients are unable to write files to an NFS share with NFSv3
      https://kb.netapp.com/on-prem/ontap/da/NAS/NAS-KBs/Unix_clients_are_unable_to_write_files_to_an_NFS_share_with_NFSv3
      Applies to ONTAP 9 NFSv3 Issue Unix clients are unable to write specific shares to NFS shares, although they can mount, traverse, read and write most files. The file locking (flock) command hangs