[email protected] wrote: > bl4: >> Yes, /etc/default/auplink seems to fix it, not only with /var but with / >> too. I didn't have to add sync. Which makes me wonder why, because I had >> /etc/default/auplink all the time on my first virtual machine. > > Do you mean that you could succeed fsck BEFORE unmounting?
In /var, unmounting had no effect on results. When it failed after remount -ro, it also failed after umount. Currently fsck after remount -ro succeeds. > Now I'd ask you to review the aufs manual. Particulary the note about > shutdown. > > If you configured /etc/default/auplink and executed "mount -no > remount,ro /" as described, then you would not meet the problem, I am > afraid. > If you think the description in the manual is not good and enough, > please advise me. I had read this part of the manual. In my first email it was one of the things that I tried and didn't help. If I remember correctly, errors about "orphaned inodes" disappeared, but there were still "bitmap differences". I can't remember if I had /etc/default/auplink at that time. In my current configuration, I don't remount / or /rw at all. Perhaps there are more conditions that must be met to get clean results in fsck. -- bl4 ------------------------------------------------------------------------------ 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
