TASK OK but lxc container not started in 4.0, no dsik capacity value

[yugawara]

Dear


I am testing a convert of CentOs base openVZ container from 3.4 to 4.0.


The CT is working fine in 3.4, but backup/restored CT does not start at 4.0.



In both case, it looks "/etc/pve/nodes/proc40/lxc/XXX.conf" has no DISK CAPACITY value.


How can I add the "Dsik Capacity value" to XXX.conf?


Someone advice me?




yugawara

 

[yugawara]

Sorry !!


Sorry my first issue was incorrect. The disk capacity value is existed.


The restored CL started with status "TASK OK".
However it never had started.


The sysylog showed as followings.
proc40 kernel: EXT4-fs (loop0): couldn't mount as ext3 due to feature incompatibilities
proc40 kernel: EXT4-fs (loop0): couldn't mount as ext2 due to feature incompatibilities
proc40 kernel: EXT4-fs (loop0): mounted filesystem with ordered data mode. Opts: (null)


The task viewer of both CTs are same as followings.
lxc-start: lxc_start.c: main: 344 The container failed to start.
lxc-start: lxc_start.c: main: 346 To get more details, run the container in foreground mode.
lxc-start: lxc_start.c: main: 348 Additional information can be obtained by setting the --logfile and --logpriority options.
TASK OK


Someone advice me?


yugawara

 

[yugawara]

Now I think the cause of this problem might be separately.


Please close this, and see anothe issue;

cannot find "Quota UGID limit" field in 4.0 lxc .....
----------------------------------------------------------


Thank you. yugawara