Jacob Burkamper: > I will collect the rest of the the information and get back to you.
I had better explain what I am thinking. Here is the plan in my mind. - identify the file which makes /ro busy. - the file may not be single. - since rsync as a process already terminated, rsync itself cannot make /ro busy. - there may exist other process(es) related to rsync or the identifed file. - generally rsync communicates with the daemon. but your case doesn't have a remote side. so there should not exist the rsync daemon process. - by setting udba=notify to aufs and auctually modify the files bypassing aufs, the notify events fired internally and aufs starts handling the event asynchoronously. But this handling should not make /ro busy. Currently I don't know what makes /ro busy. The purpose of this investigation is to make it clear. J. R. Okajima ------------------------------------------------------------------------------
