bl4: > Actually the find+rm should not modify /rw because the sed changes all > paths from /rw to /ro. The purpose of this script is to preserve all > changes (including removals) after reboot. Anyway, when I run rsync > only, I also get these errors.
I see. > > When you restore the find+rm, or if there is another process which > > writes to aufs between two fsck-s, then you need to specify udba=inotify > > before rsync. You can reset it by specifying udba=reval after second > > fsck, if you want. How about other processes? Are there any other process which writes to /, /rw or /ro? Does your rsync write any log to somewhere in aufs? > I have FLUSH=ALL in /etc/defaults/aufs and I have /sbin/mount.aufs, > which is enough according to the manpage. If you don't run remount/umount aufs or auplink manually, pseudo-link will not be flushed. J. R. Okajima ------------------------------------------------------------------------------ Download Intel® Parallel Studio Eval Try the new software tools for yourself. Speed compiling, find bugs proactively, and fine-tune applications for parallel performance. See why Intel Parallel Studio got high marks during beta. http://p.sf.net/sfu/intel-sw-dev
