> Let me make sure. > You wrote that you specified noplink and nowarn_perm. > Are you sure that you didn't specify noxino? > If you specified noxino mount option, aufs would behave like that. > And you are creating a file by creat(2) instead of link(2), aren't you?
I do not specify any "xino" option in mount. According to man aufs, xino is created on the first rw branch. I also have /sys/fs/aufs/si_c30a7c19/xino. To create files, I simply do "touch myfile", and I am not sure whether it uses creat or link, however the file created is not a link of any kind. I even do "echo aaaa > myfile", same result. >And your warning is about 'rules.d'. >Is this dir the one your nautilus monitors? No, I infact have no idea why the warning occurs on rules.d. The dir that nautilus CONSTANTLY monitors is ~/Desktop, the desktop directory. This directory is created dynamically by nautilus and does not exist beforehand. If you open a nautilus browser in a directory, nautilus will also monitor that. In all cases, ~/Desktop will always lose inotify, and if you leave a nautilus browser open on any directory long enough, that will also lose inotify, in otherwords, it can be any directory, as long as its being monitored. If you dont mind, could you please explain a little about the bugfix on 20080929: - bugfix: under heavy load the dead inode might be re-used because of the race condition between S_DEAD flag and some lock-free oprations. force 'must-new' inode in some cases. Maybe there is a missing case that is not handled in au_new_inode with regards to the must_new logic. Is there a test case that can cause this bug to occur? ------------------------------------------------------------------------- This SF.Net email is sponsored by the Moblin Your Move Developer's challenge Build the coolest Linux based applications with Moblin SDK & win great prizes Grand prize is a trip for two to an Open Source event anywhere in the world http://moblin-contest.org/redirect.php?banner_id=100&url=/
