Hi list
I'm not sure that is really an aufs issue but I think so.
In the puppylinux (aufs2.1-31 or 35) shutdown process, the journal of the boot
device (if it has an ext3 file system) stays open, or at least some files leave
behind the "open flag" bit. This triggers a boot device journal recovery in
every boot. The file system per se is clean however. Is just the journal that
is not properly closed because of some open files.
Trying to remount the boot device during shutdown read-only, fails always with
"device is busy".
However there are no open files at least as far as `lsof' or `ps' can tell.
The `.aufs.xino' is usually in dev_rw, but remounting read-only does not solve
the problem.
Trying to umount the loop devices that are different branches in aufs fails
because they are "busy". So I think that the original read-only sfs files that
are mounted on the loops and reside in the boot device may be the problem. But
I'm not really sure I understand the whole process...
So if you have any idea either diagnosing the cause of the problem more
accurately making sure that aufs might not interfere please let me know
Thx
------------------------------------------------------------------------------
The ultimate all-in-one performance toolkit: Intel(R) Parallel Studio XE:
Pinpoint memory and threading errors before they happen.
Find and fix more than 250 security defects in the development cycle.
Locate bottlenecks in serial and parallel code that limit performance.
http://p.sf.net/sfu/intel-dev2devfeb
