Good evening, I'm looking into the inability to rename a directory that is used as an aufs mountpoint, after the aufs volume has been unmounted - it reports that the 'device is busy'. The problem shows itself so far as a refcnt on the aufs module of 1, after this single aufs volume has been successfully umounted.
The problem doesn't occur if the single aufs volume isn't mounted automatically at boot via fstab, and when it is, the failure is demonstrable before I log in with X. I started with tracing the kernel module_get and module_put calls after reading http://stackoverflow.com/a/15494206/1188444 and using the following in '/etc/rc.local': ====================================================================== nohup trace-cmd record -e 'module:module_put' -f 'name == aufs' -e 'module:module_get' -f 'name == aufs' -o '/mnt/storage-1/tmp/aufs-reference-test.dat' >/dev/null & ====================================================================== This works well to list the processes that cause references to be opened and closed against the module after login, but doesn't appear to be triggered early enough to catch the single reference prior to this point. Before I go any deeper, does anyone know of a better way to attack this issue? This isn't a bug report (more a sysadmin thing), but for completeness' sake: uname -a (Debian Testing machine): Linux 3.16.0-4-amd64 #1 SMP Debian 3.16.7-ckt2-1 (2014-12-08) x86_64 GNU/Linux aufs version from kern.log: 3.16-20140908 Thanks
signature.asc
Description: OpenPGP digital signature
------------------------------------------------------------------------------ Dive into the World of Parallel Programming. The Go Parallel Website, sponsored by Intel and developed in partnership with Slashdot Media, is your hub for all things parallel software development, from weekly thought leadership blogs to news, videos, case studies, tutorials and more. Take a look and join the conversation now. http://goparallel.sourceforge.net/
