Cyanrigger: > Actually, I posted that in my last post. > But I copy it up to here for readabilitys sake: > http://pastebin.com/b5361Kk5 > > Here is the rsync-script I use again: > http://pastebin.com/X4yuqYuk
Thanks. Currently, I think "remount,ro ext3" should fail as the simple dd script did, but your rsync script didn't. I don't know why, but I guess this symptom is related to your problem. Anyway there will be several possible solutions for you. Of course, they are all based on my current guess. - Before running the rsync script, kill all processes which keep opening the file on the lower ext3, for example syslogd in your case. Restart it after the rsync script. - Introduce a feature into aufs, which copyup a file at open. actually there was such feature in aufs1, but it was removed from aufs2. It may be time to revive "coo=" mount option. With this feature, syslogd won't open the files on the lower ext3. But _if_ another process opens a dir which exists on the lower ext3 (regardless the dir exists on the upper branch) and rsync removes the dir, then the problem will appear again. - and more, maybe... By the way, if I send you a patch to investigate more, would you test it? The patch will be against aufs, vfs or ext3 and do nothing but print some messages. J. R. Okajima ------------------------------------------------------------------------------ Increase Visibility of Your 3D Game App & Earn a Chance To Win $500! Tap into the largest installed PC base & get more eyes on your game by optimizing for Intel(R) Graphics Technology. Get started today with the Intel(R) Software Partner Program. Five $500 cash prizes are up for grabs. http://p.sf.net/sfu/intelisp-dev2dev
