[email protected] wrote: >> bl4: >>> For testing, /var can be put on a separate partition and mounted as >>> aufs. It is always written to and it can be unmounted on shutdown. >> ::: >>>> By the way, I could not find /etc/default/auplink. So I had to create it >>>> manually. >>> Does it matter if the scripts call auplink manually? >> I could reproduce the problem on /var. >> But after setting /etc/default/auplink, it disappeared. >> Please try. > > Forgot to write. > I also added "sync,dirsync" mount options at remounting RW /varro, and > insert "sync" some places in aufs-var-sync.
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. Possible explanation: with /etc/default/auplink AND ext3 it works. With /etc/default/auplink and ext2 it doesn't. You can find out if you add rootfstype=ext2 in the bootloader. This looked very complicated from the beginning. Indeed there might be some bugs in the kernel which affect aufs more than other filesystems. I'm not sure if this setup is safe enough to put on an appliance. Some distributions pivot back to initrd where it's possible to unmount root and do some operations afterwards. But debian wipes out and overmounts initramfs. Another option: On shutdown, /rw is copied to another disk partition. On next boot, in initramfs, rsync is run with that copy before mounting aufs. I only tested it for a short time but it worked very well. -- 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
