Search results

Certainly the container is writing to to its disk. There is an adjustment of limits for MySQL DB in /lib/systemd/system/mysql.service. Could that be a reason? Anyway, I have a feeling that the graph was not shown since the CT was started, even before change to the limits above.

Here it is: # cat /sys/fs/cgroup/blkio/lxc/100/ns/blkio.throttle.io_service_bytes 253:0 Read 0 253:0 Write 0 253:0 Sync 0 253:0 Async 0 253:0 Total 0 253:1 Read 12288 253:1 Write 0 253:1 Sync 12288 253:1 Async 0 253:1 Total 12288 8:0 Read 94404608 8:0 Write 0 8:0 Sync 94404608 8:0 Async 0 8:0...

Sure. Problematic one: # pct status 100 --verbose cpu: 0 cpus: 10 disk: 35379212288 diskread: 377593856 diskwrite: 0 lock: maxdisk: 84014424064 maxmem: 21474836480 maxswap: 4294967296 mem: 10847776768 name: xxx netin: 237837656180 netout: 1584474138588 pid: 9194 status: running swap: 22663168...

Thanks for reply. The node is freshly setup - last week. 2 of the CTs that are showing I/O fine were migrated from an older node (3.1). 2 other CTs are newly created at the node. For one of these I/O graph works, for other not. (both started from the same template, Ubuntu 16.04, same way) All...

Running proxmox 5.1. I have 4 CTs on one node, all of them running Ubuntu. One of this CT does not show I/O stats in Proxmox GUI, the other 3 do. Any ideas what to check, what may be wrong?

Migrating from Proxmox 3.1 to 5.1. Successfully migrated couple of Ubuntu containers already. Now stuck with Centos (6.x) container - migration went ok, but after container start, no access via console or network. Using debug, looks like it hangs at: lxc-start 102 20171029185125.850 NOTICE...