Ben Hutchings: > This doesn't look like a failure, it looks like a warning about a case > where aufs is not very efficient.
Exactly. > aufs appears to maintain a single list of pseudo links per aufs > filesystem, which will make it slow whenever there are a lot of them. > Hence the warning. Not only the speed, but also the space. To implement the "pseudo-link", aufs keeps the inode on memory. So the large number of pseudo-links can be memory pressure. Hence the warning. As you might know, the pseudo-links on memory are flushed (and free the memory) when you run the auplink utility manually or remount aufs with different options (not all kinds of options). For this warning, I remember someone else had ever asked "what is this?" or something. It means this warning and behaviour may confuse users. So I will try refining it when I have time. Currently when the number of psuedo-links reaches 100, aufs warns. The new behaviour will be, for example, - the warning is produced when the number of pseudo-link reaches 50% (?) of /proc/sys/fs/inode-brabra (the maximum number of the cache-able inodes). - the number should be dynamically customizable by user. - of course, as Ben Hutchings wrote in another mail, in order to support the case when the large number is specifed, the data structure needs to be refined. J. R. Okajima ------------------------------------------------------------------------------ Minimize network downtime and maximize team effectiveness. Reduce network management and security costs.Learn how to hire the most talented Cisco Certified professionals. Visit the Employer Resources Portal http://www.cisco.com/web/learning/employer_resources/index.html
