Hello Richard, Richard Mills: > The problem is that after a few days of running, random binaries on the > system start to have problems. For example; today gdb SEGVs every time it is > run. Here is an strace of running up gdb:
According to your /proc/mounts, you have three aufses, /home, /root and /var. And your gdb binary exists in /usr/bin/gdb which means out of aufs. Also I guess all of shared libraries (and related ones), - /etc/ld.so.preload - /etc/ld.so.cache - /usr/lib/libncurses.so.5 - /lib/libtermcap.so.2 - /lib/tls/libm.so.6 - /lib/libdl.so.2 - /lib/tls/libc.so.6 are all out of aufs. I don't understand why you thought this is aufs problem. I'd suggest you to check your system. Otherwise give me these info. (from aufs README) ---------------------------------------------------------------------- - /proc/mounts (instead of the output of mount(8)) - /sys/module/aufs/* - /sys/fs/aufs/* (if you have them) - /debug/aufs/* (if you have them) - linux kernel version if your kernel is not plain, for example modified by distributor, the url where i can download its source is necessary too. - aufs version which was printed at loading the module or booting the system, instead of the date you downloaded. - configuration (define/undefine CONFIG_AUFS_xxx) - kernel configuration or /proc/config.gz (if you have it) - behaviour which you think to be incorrect - actual operation, reproducible one is better ---------------------------------------------------------------------- J. R. Okajima ------------------------------------------------------------------------------ This SF.Net email is sponsored by the Verizon Developer Community Take advantage of Verizon's best-in-class app development support A streamlined, 14 day to market process makes app distribution fast and easy Join now and get one step closer to millions of Verizon customers http://p.sf.net/sfu/verizon-dev2dev
