Package: munin
Version: 2.0.0-1
Severity: normal
Tags: upstream

There's a problem with the df plugin on Wheezy OpenVZ guests though it's
probably not limited to those.

OpenVZ on Squeeze exposes some "virtual" filesystems, including the 
quota-enhanced root filesystem and tmpfs, as "/dev/simfs" to the guest.

This causes the df plugin to trip over since it expects all mount
entries whose device name starts with a / to be unique and uses the
device name as internal name.

In squeeze and earlier this wasn't an issue since most guests usually
had only one /dev/simfs entry, that being the root device.

With wheezy /run and /run/lock are added, causing the problems as seen
below.


A possible mitigation mechanism could be to treat "/dev/simfs"
entries the same like tmpfs entries and fall back on just using the
mountpoint for those. Though I'm not sure that the outlook of OpenVZ
warrants this hackaround.


Here are the example /proc/mounts and "config df" outputs of two
systems:


Squeeze OpenVZ guest

/dev/simfs / simfs rw,relatime 0 0
proc /proc proc rw,relatime 0 0
sysfs /sys sysfs rw,relatime 0 0
tmpfs /lib/init/rw tmpfs rw,nosuid,relatime,mode=755 0 0
tmpfs /dev/shm tmpfs rw,nosuid,nodev,relatime 0 0
devpts /dev/pts devpts rw,nosuid,noexec,relatime,gid=5,mode=620 0 0
/dev/simfs /run simfs rw,relatime 0 0
/dev/simfs /run/lock simfs rw,relatime 0 0
tmpfs /run/shm tmpfs rw,nosuid,nodev,relatime 0 0

_dev_simfs.label /
_dev_simfs.warning 92
_dev_simfs.critical 98
_lib_init_rw.label /lib/init/rw
_lib_init_rw.warning 92
_lib_init_rw.critical 98
_dev_shm.label /dev/shm
_dev_shm.warning 92
_dev_shm.critical 98
_dev_simfs.label /run
_dev_simfs.warning 92
_dev_simfs.critical 98
_dev_simfs.label /run/lock
_dev_simfs.warning 92
_dev_simfs.critical 98
_run_shm.label /run/shm
_run_shm.warning 92
_run_shm.critical 98


Squeeze on bare metal

rootfs / rootfs rw 0 0
sysfs /sys sysfs rw,nosuid,nodev,noexec,relatime 0 0
proc /proc proc rw,nosuid,nodev,noexec,relatime 0 0
udev /dev devtmpfs rw,relatime,size=4092364k,nr_inodes=1023091,mode=755 0 0
devpts /dev/pts devpts rw,nosuid,noexec,relatime,gid=5,mode=620,ptmxmode=000 0 0
tmpfs /run tmpfs rw,nosuid,noexec,relatime,size=819720k,mode=755 0 0
/dev/mapper/VGroot-LVroot / ext3 
rw,noatime,errors=remount-ro,barrier=1,data=ordered 0 0
tmpfs /run/lock tmpfs rw,nosuid,nodev,noexec,relatime,size=5120k 0 0
tmpfs /tmp tmpfs rw,nosuid,nodev,relatime,size=1639440k 0 0
proc /proc proc rw,nosuid,nodev,noexec,relatime 0 0
sysfs /sys sysfs rw,nosuid,nodev,noexec,relatime 0 0
tmpfs /run/shm tmpfs rw,nosuid,nodev,relatime,size=1639440k 0 0
debugfs /sys/kernel/debug debugfs rw,relatime 0 0


rootfs.label /
rootfs.warning 92
rootfs.critical 98
_dev.label /dev
_dev.warning 92
_dev.critical 98
_run.label /run
_run.warning 92
_run.critical 98
_dev_mapper_VGroot_LVroot.label /
_dev_mapper_VGroot_LVroot.warning 92
_dev_mapper_VGroot_LVroot.critical 98
_run_lock.label /run/lock
_run_lock.warning 92
_run_lock.critical 98
_tmp.label /tmp
_tmp.warning 92
_tmp.critical 98
_run_shm.label /run/shm
_run_shm.warning 92
_run_shm.critical 98


all the best,
Michael



-- 
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org

Reply via email to