Proxmox 2.3, Windows Storage Server 2012, Samba Shares, and File Lock Troubles

[riptide_wave]

Hello,

So long story short I am trying to use a SMB network storage to host VM's from for live migration. I created the share in the /etc/fstab, mounted it successfully, and am able to read and write from the share with no problem. I am even able to create and restore backups without a problem, the thing is when I try to create a VM, or restore a VM to the storage, I get the following error:

When creating a KVM:

[COLOR=#000000][FONT=tahoma]TASK ERROR: create failed - unable to create image: got lock timeout - aborting command[/FONT][/COLOR]

When restoring a KVM:

[COLOR=#000000][FONT=tahoma]restore vma archive: lzop -d -c /var/lib/vz/dump/vzdump-qemu-106-2013_03_21-15_13_42.vma.lzo|vma extract -v -r /var/tmp/vzdumptmp247935.fifo - /var/tmp/vzdumptmp247935[/FONT][/COLOR]
[COLOR=#000000][FONT=tahoma]CFG: size: 311 name: qemu-server.conf[/FONT][/COLOR]
[COLOR=#000000][FONT=tahoma]DEV: dev_id=1 size: 17179869184 devname: drive-ide0[/FONT][/COLOR]
[COLOR=#000000][FONT=tahoma]CTIME: Thu Mar 21 15:13:44 2013[/FONT][/COLOR]
[COLOR=#000000][FONT=tahoma]TASK ERROR: command 'lzop -d -c /var/lib/vz/dump/vzdump-qemu-106-2013_03_21-15_13_42.vma.lzo|vma extract -v -r /var/tmp/vzdumptmp247935.fifo - /var/tmp/vzdumptmp247935' failed: unable to create image: got lock timeout - aborting command[/FONT][/COLOR]

But it shows the qcow2 file when I check the storage, so the file was created and was expanded to the proper size. I verified the user account the nodes use to mount the storage have full access, and that it applies to all files and folders.

I am using this in a cluster of 2 nodes, and both have the same problem.

pveversion -v

root@srv-1-02:~# pveversion -vpve-manager: 2.3-13 (pve-manager/2.3/7946f1f1)
running kernel: 2.6.32-18-pve
proxmox-ve-2.6.32: 2.3-88
pve-kernel-2.6.32-18-pve: 2.6.32-88
lvm2: 2.02.95-1pve2
clvm: 2.02.95-1pve2
corosync-pve: 1.4.4-4
openais-pve: 1.1.4-2
libqb: 0.10.1-2
redhat-cluster-pve: 3.1.93-2
resource-agents-pve: 3.9.2-3
fence-agents-pve: 3.1.9-1
pve-cluster: 1.0-36
qemu-server: 2.3-18
pve-firmware: 1.0-21
libpve-common-perl: 1.0-48
libpve-access-control: 1.0-26
libpve-storage-perl: 2.3-6
vncterm: 1.0-3
vzctl: 4.0-1pve2
vzprocps: 2.0.11-2
vzquota: 3.1-1
pve-qemu-kvm: 1.4-8
ksm-control-daemon: 1.1-1

Thanks

 

[dietmar]

What is the output of

# pcecm nodes

and

# pvecm status

 

[riptide_wave]

pvecm nodes

mroot@srv-1-02:~# pvecm nodes
Node  Sts   Inc   Joined               Name
   1   M    632   2013-03-21 17:12:49  srv-1-02
   2   M    672   2013-03-21 17:13:21  srv-1-03

pvecm status

root@srv-1-02:~# pvecm statusVersion: 6.2.0
Config Version: 2
Cluster Name: Cluster-1
Cluster Id: 45403
Cluster Member: Yes
Cluster Generation: 672
Membership state: Cluster-Member
Nodes: 2
Expected votes: 2
Total votes: 2
Node votes: 1
Quorum: 2
Active subsystems: 5
Flags:
Ports Bound: 0
Node name: srv-1-02
Node ID: 1
Multicast addresses: 239.192.177.13
Node addresses: 10.1.6.2

 

[dietmar]

I assume a restore to local storage works?

 

[riptide_wave]

yes, restores and creations to local storage work without a hitch.

Also, here is what is in my fstab to mount the drive

//10.1.8.1/Storage /mnt/NFS-SMB cifs username=user,password=pass 0 0

 

[dietmar]

yes, restores and creations to local storage work without a hitch.

Just for testing, does it work if you remove the 'shared' flag on the storage (re-add the flag after testing).

 

[riptide_wave]

Nope, still have the same problem.

(just a note, I decided to give up and moved my storage box to a new distro, all working now)

I still have a box with server 2012 with the same problem though when mounted. if you care to continue debugging this we can, but technically its no longer required.

 

[gansc]

Hi,

i have the same problem. I used a NFS share on a Windows SBS2011 add and mount no problem.
When i create a VM i get the error:
TASK ERROR: create failed - unable to create image: got lock timeout - aborting command

I Use Proxmox V 2.3 all updates.

The remote Filesystem is NTFS (SBS2011) -> NFS -> Proxmox. With iSCSI and LVM it works!

Maybe it helps: I test to create a 10 GB cow2 Image. The image was build but it raise the error.

Can anybody help?

Thanks a lot!


Best regards
Christian

 

[mijohnst]

This is an old thread, but I've noticed that I have the same problem on my NAS. I can manually mount it and create/delete anything it from a host, but if I try to clone or created a new VM it fails. I'm using 4.4. My NAS is a Buffalo TeraStation 5500.

Task viewer: VM 100 - Clone

OutputStatus

Stop
create full clone of drive scsi0 (gluster:100/vm-100-disk-1.qcow2)
TASK ERROR: clone failed: unable to create image: got lock timeout - aborting command