>> No. The read-only remount goes ahead fine, but while shutdown I get
>> the same errors:
> :::
>> /dev/hda1:Superblock last mount time is in the future. FIXED.
>> /dev/hda1:Superblock last write time is in the future. FIXED.
>> /dev/hda1: clean, xxx files, yyy blocks [ OK ]
>
> Really?
> If "mount -o remount,ro /sysroot" really succeeded but fsck reported
> error, then the problem is out of aufs...
>
No, what I meant was that the aufs remount went fine:
"mount -o remount,ro,mod:/bin=ro /aufs/bin"
I'm not remounting root fs ( / ) read-only.
Ok, Let me ask a specific question: Given my situation ( after the
system is up and I've logged on in a shell), is there a way to unmount
the union of /aufs/{bin,sbin....} and /.mount/{bin,sbin....}, so that
the system is running again from /.mount/{sbin,sbin...} ?
Thanks,
Nitin.
------------------------------------------------------------------------------
Create and Deploy Rich Internet Apps outside the browser with Adobe(R)AIR(TM)
software. With Adobe AIR, Ajax developers can use existing skills and code to
build responsive, highly engaging applications that combine the power of local
resources and data with the reach of the web. Download the Adobe AIR SDK and
Ajax docs to start building applications today-http://p.sf.net/sfu/adobe-com
