[openvz] fs.aio-max-nr

jmginer

Quick, why to modify?:

http://forum.openvz.org/index.php?t=msg&goto=44068

https://bugzilla.openvz.org/show_bug.cgi?id=2953

The current issue?

https://bugzilla.openvz.org/show_bug.cgi?id=3161

Fixed? Seems yes, here:

https://openvz.org/Download/kernel/rhel6/042stab094.7/changes

fs/aio: aio_nr & aio_max_nr variables virtualization (PSBM-27188)
fs/aio: introduce aio_nr & aio_max_nr per-CT sysctls (PSBM-27188)

But, how to do? I don't find any documentation

Any idea?

Thanks!

jmginer

Workaround, create a CTID.start script for the container who wants increase his fs.aio-max-nr value and add:

sysctl -w fs.aio-max-nr=1000000

If you want for all containers in your HN, run cron job, every 5 minutes:

#! /bin/bash
export PATH="/usr/kerberos/sbin:/usr/kerberos/bin:/usr/local/sbin:/usr/local/bin:/sbin:/bin:/usr/sbin:/usr/bin:/root/bin"

cd /etc/vz/conf; rm -rf *.start;
ls /vz/private | cat > vzlist.txt;
cat vzlist.txt | while read line; do
echo "sysctl -w fs.aio-max-nr=1000000" > ${line}.start;
chmod 755 ${line}.start;
done

So, for a new container creation, the customer only need to wait a bit (the cronjob delay) and do a stop/start of their VPS.

If anybody know other method, I'm pleased to know

Regards!!

0xdragon

Why not just do:

sysctl -w fs.aio-max-nr=1048576 >> /etc/sysctl.conf

On the host node?

jmginer

@0xdragon said:
Why not just do:

sysctl -w fs.aio-max-nr=1048576 >> /etc/sysctl.conf

On the host node?

Not run, check this:
https://bugzilla.openvz.org/show_bug.cgi?id=3161