I was just coming here to report the issue of the .Trash directories as well. However, I only have about 15 automount entries on my system so I don't see the same kinds of load problems seen by robogeek. I just noticed that my daemon.log file is filling up with autofs errors:
Apr 4 16:14:41 psmith-ubeta automount[3093]: failed to mount /export/autofs/.Trash Apr 4 16:14:41 psmith-ubeta automount[3094]: failed to mount /export/autofs/.Trash-10490 Apr 4 16:14:41 psmith-ubeta automount[3099]: >> /sbin/showmount: can't get address for .Trash Apr 4 16:14:41 psmith-ubeta automount[3099]: lookup(program): lookup for .Trash failed Apr 4 16:14:41 psmith-ubeta automount[3099]: failed to mount /net/.Trash Apr 4 16:14:41 psmith-ubeta automount[3105]: >> /sbin/showmount: can't get address for .Trash-10490 Apr 4 16:14:41 psmith-ubeta automount[3105]: lookup(program): lookup for .Trash-10490 failed Apr 4 16:14:41 psmith-ubeta automount[3105]: failed to mount /net/.Trash-10490 Apr 4 16:14:41 psmith-ubeta automount[3111]: failed to mount /opt/net/.Trash Apr 4 16:14:41 psmith-ubeta automount[3112]: failed to mount /opt/net/.Trash-10490 etc. Note that 10490 is my UID. This seems to happen every time automount tries to mount something. It looks like some kind of bad interaction between the new trashcan capabilities (maybe gvfs) I've heard about, and autofs. It might not be an autofs problem at all, but I don't know what part of the system is trying to access the .Trash directory on every filesystem, and where that process, whatever it is, gets its list of filesystems to test. This is a big problem for people trying to use Ubuntu in any kind of traditional enterprise environment, where autofs is ubiquitous. -- Hi load average using in 8.04a4 NIS/Autofs setup copied from 7.10 https://bugs.launchpad.net/bugs/190737 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
