OpenVZ Forum


Home » General » Support » VE migration failed: Can not dump VE: d_path is invisible
Re: VE migration failed: Can not dump VE: d_path is invisible [message #33133 is a reply to message #33132] Wed, 24 September 2008 11:32 Go to previous message
januszzz is currently offline  januszzz
Messages: 50
Registered: January 2007
Location: Opole, Poland
Member
Well, I didn't have any extra mounts, just plain system with fifos, I found that each of the fifo was stopper for OpenVZ, but...

...but I find OpenVZ migration extremely frustrating now, because this message has gone just after reboot of those machines (HEs)!!

Anyway, I'm having more errors now:

vzmigrate -v -r no --online 126.66.64.64 123
OPT:-v
OPT:-r
OPT:--online
OPT:126.66.64.64
Starting online migration of VE 123 on 126.66.64.64
* status: started
Loading /etc/vz/vz.conf and /etc/vz/conf/123.conf files
Check IPs on destination node: 126.66.64.152
Preparing remote node
Copying config file
123.conf 100% 1708 1.7KB/s 00:00
Saved parameters for VE 123
/usr/sbin/vzmigrate: line 382: [: missing `]'
Creating remote VE root dir
Creating remote VE private dir
VZ disk quota disabled -- skipping quota migration
Syncing private
Live migrating VE
Suspending VE
Setting up checkpoint...
suspend...
get context...
Checkpointing completed succesfully
Dumping VE
Setting up checkpoint...
join context..
dump...
Checkpointing completed succesfully
Copying dumpfile
dump.123 100% 160MB 11.5MB/s 00:14
Syncing private (2nd pass)
VZ disk quota disabled -- skipping quota migration
Undumping VE
Restoring VE ...
Starting VE ...
VE is mounted
undump...
Adding IP address(es): 126.66.64.152
Setting CPU units: 1000
Configure meminfo: 131072
Error: undump failed: No space left on device
Restoring failed:
Stopping VE ...
Error: do_rst_mm 14927288
Error: rst_mm: -28
Error: make_baby: -28
Error: rst_clone_children
Error: make_baby: -28
Error: rst_clone_children
Error: make_baby: -28
Error: rst_clone_children
Error: make_baby: -28
Error: rst_clone_children
Error: make_baby: -28
Error: rst_clone_children
Error: make_baby: -28
Error: rst_clone_children
Error: make_baby: -28
Error: rst_clone_children
Error: make_baby: -28
Error: rst_clone_children
Error: make_baby: -28
Error: rst_clone_children
Error: make_baby: -28
Error: rst_clone_children
VE start failed
VE was stopped
VE is unmounted
Error: Failed to undump VE
Resuming...
arpsend: 126.66.64.152 is detected on another computer : 00:1c:23:27:03:bf
vps-net_add WARNING: arpsend -c 1 -w 1 -D -e 126.66.64.152 eth0 FAILED

and this is even though I got ~15 GB free on both disks (source/destination) Isn't it for new thread?

EDIT: ...and the error is not permanent, replying the command gives other messages each time:

[...]
adding IP address(es): 126.66.64.152
Setting CPU units: 1000
Configure meminfo: 131072
Error: undump failed: No space left on device
Restoring failed:
Error: do_rst_mm 27294312
Error: rst_mm: -28
Error: make_baby: -28
Error: rst_clone_children
Stopping VE ...
VE start failed
VE was stopped
VE is unmounted
Error: Failed to undump VE
Resuming...
arpsend: 126.66.64.152 is detected on another computer : 00:1c:23:27:03:bf
vps-net_add WARNING: arpsend -c 1 -w 1 -D -e 126.66.64.152 eth0 FAILED

On the second HN (126.66.64.64) I get
CPT ERR: xxxxxxxxxxxxx,123 : do_rst_mm xxxxx
rst_mm: -28
make_baby: -28
rst_clone_children

and the like.

[Updated on: Wed, 24 September 2008 12:06]

Report message to a moderator

 
Read Message
Read Message
Read Message
Previous Topic: privvmpages are failing even if barrier and limit are high enough
Next Topic: ovzkernel conflicts with dev < 3.2-7
Goto Forum:
  


Current Time: Fri Aug 22 04:35:55 GMT 2025

Total time taken to generate the page: 0.05731 seconds