hi,
the following was recently observed at least on the following
x86 platforms:
2.6.15-vs2.1.0.5 (gcc 3.4.4)
2.6.16-rc1-vs2.1.0.7 (gcc 4.0.3)
it does NOT happen under
2.6.14-vs2.1.0 (gcc 3.4.4)
patchlevels in between not tested yet.
symptons: context names stored in the kernel get corrupted,
rendering the vserver tools almost unusable, at least when not using any
legacy (tried 0.30.209 and 0.30.210)
vuname and vserver-info ... CONTEXT false simply fail
Bertl pinned it down to some kernel level issue:
Jan 27 12:03:32 moon kernel: vxD: __lookup_vx_info(#101):
ffff81007cb7f000[#101] »/etc/vservers/test101«
[cut]
Jan 27 12:03:32 moon kernel: vxD: __lookup_vx_info(#101):
ffff81007cb7f000[#101] »/etc/vservers/tevt101«
[cut]
Jan 27 12:03:32 moon kernel: vxD: __lookup_vx_info(#101):
ffff81007cb7f000[#101] »/etc/vservers/tee}101«
more info at:
http://vserver.13thfloor.at/Stuff/BUGHUNT/cohan-0001/klog.txt
http://vserver.13thfloor.at/Stuff/BUGHUNT/cohan-0001/klog2.txt
cu,
cohan
_______________________________________________
Vserver mailing list
Vserver@list.linux-vserver.org
http://list.linux-vserver.org/mailman/listinfo/vserver