After nightly backup VM don't start. sos

[Deni74]

Hello.
After nightly backup VM don't wont start. Web interface - not working - first time - connection failure, now - login failed.
In SSH session:

qm unlock 300 - ok
qm status 300 - stoped
qm start 300 - without response
(host name BACKUP too)
in logs -
backup qm [56059]: <root@pam> starting task UPID:backup:xxxxx:xxxxx:xxxxx:qmstart:300:root@pam:
backup qm [56059]: <root@pam> end task UPID:backup:xxxxx:xxxxx:xxxxx:qmstart:300:root@pam: unable to read tail (got 0 bytes)
.........
disks not full.
Temporary VM 300 is located on the same nfs storage(name backup) on which there was backup error.
pvesm status - - without response

HELP!

Thanx!

 

[udo]

Hello.
After nightly backup VM don't wont start. Web interface - not working - first time - connection failure, now - login failed.
In SSH session:

qm unlock 300 - ok
qm status 300 - stoped
qm start 300 - without response
(host name BACKUP too)
in logs -
backup qm [56059]: <root@pam> starting task UPID:backup:xxxxx:xxxxx:xxxxx:qmstart:300:root@pam:
backup qm [56059]: <root@pam> end task UPID:backup:xxxxx:xxxxx:xxxxx:qmstart:300:root@pam: unable to read tail (got 0 bytes)
.........
disks not full.
расположена на том же storage на котором произошла ошибка
Temporary VM 300 is located on the same nfs storage(name backup) on which there was backup error.
pvesm status - - without response

HELP!

Thanx!

Hi,
can you post the config?

cat /etc/pve/qemu-server/300.conf

Udo

 

[Deni74]

balloon: 0
boot: c
bootdisk: sata0
cores: 2
localtime: 1
memory: 4096
name: Zentyal
net0: e1000=E2:5F:3C:2B:727,bridge=vmbr0
onboot: 1
ostype: l26
sata0: backup:300/vm-300-disk-1.raw,format=raw,cache=writeback,size=250G
sockets: 1
vga: std


backup - nfs storage (lvm based ext4), with nughtly backup error


Running process:

48359	root	02:00	task UPID:backup:0000BCE7:0068737C:5238D0E2:vzdump::root@pam:
48371	root	02:00	lzop

Kill -9 can't help - process runing
I think it's .... 2:00 - time when start error backup
Vzdump log.
Sep 18 02:00:02 INFO: Starting Backup of VM 300 (qemu)
Sep 18 02:00:02 INFO: status = running
Sep 18 02:00:03 INFO: update VM 300: -lock backup
Sep 18 02:00:03 INFO: backup mode: suspend
Sep 18 02:00:03 INFO: ionice priority: 7
Sep 18 02:00:04 INFO: suspend vm
Sep 18 02:00:04 INFO: creating archive '/mnt/pve/backup/dump/vzdump-qemu-300-2013_09_18-02_00_02.vma.lzo'

Yes I understand - it's storage problem, but i'don't know what can i do

 

[udo]

balloon: 0
boot: c
bootdisk: sata0
cores: 2
localtime: 1
memory: 4096
name: Zentyal
net0: e1000=E2:5F:3C:2B:727,bridge=vmbr0
onboot: 1
ostype: l26
sata0: backup:300/vm-300-disk-1.raw,format=raw,cache=writeback,size=250G
sockets: 1
vga: std


backup - nfs storage (lvm based ext4), with nughtly backup error


Running process:

48359	root	02:00	task UPID:backup:0000BCE7:0068737C:5238D0E2:vzdump::root@pam:
48371	root	02:00	lzop

Kill -9 can't help - process runing
I think it's .... 2:00 - time when start error backup
Vzdump log.
Sep 18 02:00:02 INFO: Starting Backup of VM 300 (qemu)
Sep 18 02:00:02 INFO: status = running
Sep 18 02:00:03 INFO: update VM 300: -lock backup
Sep 18 02:00:03 INFO: backup mode: suspend
Sep 18 02:00:03 INFO: ionice priority: 7
Sep 18 02:00:04 INFO: suspend vm
Sep 18 02:00:04 INFO: creating archive '/mnt/pve/backup/dump/vzdump-qemu-300-2013_09_18-02_00_02.vma.lzo'

Yes I understand - it's storage problem, but i'don't know what can i do

Hi,
is the disk-image allready in use?

fuser /mnt/pve/backup/images/300/vm-300-disk-1.raw

# what shows
file /mnt/pve/backup/images/300/vm-300-disk-1.raw

Udo

 

[Deni74]

Ok, kill nfs storage, unlock web gui, make new not nfs storage. Now good without restart.

What was it? What problems can be with NFS storage on LVM?

 

[udo]

What was it? What problems can be with NFS storage on LVM?

Hi,
for the pve-host is the lvm below an nfs-mount (if I understand right: nfs-server -> lvm -> filesystem -> export with nfs ) not visible.

Udo

 

[Deni74]

not visible for other PVE after buckup vm300 from NFS to same NFS. how i think. C attachement image. Mistake. I was in panic when raid 10 (12!!!!! sas hdd) die and move vm300 to NFS on PVE3 without thinking.