> Here are my suggestion due to not-so-deep thinking. > - check all /etc/rc scripts which will be executed after initramfs, > particularly /etc/fstab on your root dir. disabling most rc scripts > may be a good approach for debugging.
Putting a /bin/sh in the first rc script enabled me to test for the error with everything disabled, it is there and it it is triggered just the same. > - somewhere early stage in rc script, try re-mounting all mount-points > such like "mount -o remount /var" which will have an effect to discard > unused caches. Remounting /proc, /sys and /dev won't change the error behaviour. As I am on a Debian Squeeze system the mount.nfs command does not allow remounting of nfs-mounts. I did try an install a backport of nfs-utils without this bug, but I had trouble getting it to work. The backported version has dependencies on libraries in /usr/lib (why would anyone do that?), I could solve this by copying them over to /lib but still it won't work. http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=612933 > - you can get the similar effect by "echo 2 > /proc/sys/vm/drop_caches". This did not change the error behaviour. I will try to have a closer look at the mechanics of switching over from initramfs, maybe I can get it to trigger even there. One other option of debugging is the question, why does ls /aufs/server trigger the error and ls /aufs/client not. Both directories as mounted in the same way, client will be ro+wh in the aufs mount, server ro only, will have a look there as well, probably over the weekend. Thank you for your patience, Eibo Thieme ------------------------------------------------------------------------------ Everyone hates slow websites. So do we. Make your web apps faster with AppDynamics Download AppDynamics Lite for free today: http://p.sf.net/sfu/appdyn_d2d_feb
