----- Original Message -----
From: "Gianluca Cecchi" <gianluca.cecchi@gmail.com> To: "Dan Kenigsberg" <danken@redhat.com> Cc: "Meital Bourvine" <mbourvin@redhat.com>, barumuga@redhat.com, "users" <users@ovirt.org> Sent: Tuesday, February 4, 2014 8:46:52 PM Subject: Re: [Users] Problems with migration on a VM and not detected by gui
On Tue, Feb 4, 2014 at 3:43 PM, Dan Kenigsberg wrote:
On Tue, Feb 04, 2014 at 08:41:13AM -0500, Meital Bourvine wrote:
Hi,
Can you please open a bug about KeyError: 'path'?
Please include an excerpt of supervdsm.log, to give a better hint why glusterVolumeStatus is failing in this fashion.
here it is. https://bugzilla.redhat.com/show_bug.cgi?id=1061211
I updated the bz. It looks like glusterfs issue. Please share glusterfs version. Regards, Bala
After fsck of /boot on VM and restart I configured ntp that was not up. I successfuly migrated the VM. Only message I get in it during migration (16:07):
Feb 4 15:35:09 c6s ntpd[1510]: 0.0.0.0 c614 04 freq_mode Feb 4 15:51:35 c6s ntpd[1510]: 0.0.0.0 0612 02 freq_set kernel -0.031 PPM Feb 4 15:51:35 c6s ntpd[1510]: 0.0.0.0 0615 05 clock_sync Feb 4 16:07:33 c6s kernel: Clocksource tsc unstable (delta = -79565137 ns)
the two hosts seem almost aligned (they use chronyd):
node 1 where c6s booted # chronyc tracking Reference ID : (one-common-server in my infra) Stratum : 3 Ref time (UTC) : Tue Feb 4 15:10:05 2014 System time : 0.000015313 seconds slow of NTP time Last offset : -0.000017689 seconds RMS offset : 0.000047532 seconds Frequency : 19.180 ppm fast Residual freq : -0.004 ppm Skew : 0.146 ppm Root delay : 0.004059 seconds Root dispersion : 0.005400 seconds Update interval : 260.4 seconds Leap status : Normal
node 2 where I migrated first # chronyc tracking Reference ID : (one-common-server in my infra) Stratum : 3 Ref time (UTC) : Tue Feb 4 15:09:48 2014 System time : 0.000003940 seconds slow of NTP time Last offset : 0.000000705 seconds RMS offset : 0.000043605 seconds Frequency : 31.695 ppm fast Residual freq : -0.000 ppm Skew : 0.131 ppm Root delay : 0.004193 seconds Root dispersion : 0.005894 seconds Update interval : 128.6 seconds Leap status : Normal
MIgrating VM on the other side (from node2 to node 1 at 16:13) I don't get any message. But I do see this about two minutes after the first migration in my VM
Feb 4 16:09:03 c6s kernel: EXT4-fs error (device vda1): ext4_readdir: bad entry in directory #11: rec_len is smaller than minimal - block=4358offset=0(0), inode=0, rec_len=0, name_len=0
Donna if a problem of VM itself or related in some way with ovirt and migration.... I will investigate
Gianluca