On Thu, Feb 12, 2009 at 2:47 PM, <sf...@users.sourceforge.net> wrote: > > Nitin Bhardwaj: >> Ok.. so now at the fag end of the shutdown script I added: "mount -o >> remount,ro /" and it went fine. So now should I consider my ext3 >> filesystem on /dev/hda1 to be properly shutdown ? > > If fsck at next boot time doesn't say anything, yes it was cleanly > unmounted. > > > J. R. Okajima >
OK. I figured out the solution now, did two things: (1). I do lazy unmount of all aufs branches in the shutdown script, in this order: umount -l /usr umount -l /bin umount -l /sbin umount -l /lib (2). Set my system clock to UTC, instead of local-time. which still gives me busy errors at the end of shutdown: umount2: /tmp : Device or resource busy umount: /tmp: device is busy umount2: /sbin : Device or resource busy umount: /sbin: device is busy umount2: /lib : Device or resource busy umount: /lib: device is busy umount2: /bin : Device or resource busy umount: /bin: device is busy However, at the boot time I do not get the superblock errors now: Checking filesystems /dev/hda1: clean, xxx files, yyy blocks [ O K ] So, I guess the problem is solved now. Thanks Junjiro for all your attention,timely advice and help. One question though: Do you plan to release vendor-specific patches ( like the unionfs guys do ) for aufs2 in foreseeable future ? That way, people (like me) with vendor-specific kernels don't have to be stick with old versions of aufs. Thanks, Nitin. ------------------------------------------------------------------------------ Open Source Business Conference (OSBC), March 24-25, 2009, San Francisco, CA -OSBC tackles the biggest issue in open source: Open Sourcing the Enterprise -Strategies to boost innovation and cut costs with open source participation -Receive a $600 discount off the registration fee with the source code: SFAD http://p.sf.net/sfu/XcvMzF8H
