On Wed, Feb 11, 2009 at 11:09 AM,  <sf...@users.sourceforge.net> wrote:
>
> Nitin Bhardwaj:
>> I think you misunderstood that the problem is with  the /sysroot/bin
>> line of aufs in /etc/fstab. The problem is with /sysroot itself (
>> which eventually becomes / , after switch_root() call in the initrd ).
>> If we mount /sysroot as read-write ( as you suggest below, Step 1,
>> then rc.sysinit script runs a fsck on /, which fails because it was
>> mounted as read-write. Hence we need to mount /sysroot as read-only
>> only.
>
> Ok, then let's try tmpfs for aufs xino files.
>
> Assuming RHEL changes the root dir readwrite after fsck or something,
>        :::
> mount -t ext3 /dev/hda1 /sysroot
> mount --ro -t squashfs /dev/hda2 /sysroot/.mount
> mount -t tmpfs tmpfs /sysroot/tmp
> for i in bin lib sbin usr
> do mount -t aufs -o xino=/sysroot/tmp/xino,br:/sysroot/$i:/sysroot/.mount/$i \
>        aufs /sysroot/$i
> done
> mount -o remount,ro /sysroot
>        :::
>
> There is no changes necessary /etc/fstab, I think.
>
>
> J. R. Okajima
>

Hi,

This is finally working with some tweaks :)

[...]
mount -t ext3 /dev/hda1 /sysroot
mount --ro -t squashfs /dev/hda2 /sysroot/.mount
mount -t tmpfs /sysroot/tmp /sysroot/tmp
mount -t aufs -o
xino=/sysroot/tmp/xino,br=/sysroot/bin:/sysroot/.mount/bin=ro
/sysroot/bin /sysroot/bin
[...]
mount -t ext3 -o remount,ro /dev/hda1 /sysroot

---------------------------------
But when I shutdown, I get following errors:
umount: /bin: Device or file system busy
umount: /sbin: Device or file system busy
umount: /lib: Device or file system busy
umount: /usr: Device or file system busy

I cannot change the umount in the halt script to umount -i, otherwise
it will get applied to *ALL* filesystem types, even non-aufs types.

So now, on every boot at filesystem check I get the following message:
/dev/hda1:Superblock last mount time is in future: FIXED
/dev/hda1:Superblock last mount time is in future: FIXED
/dev/hda1: clean ....                                                [
    OK    ]

Should I be concerned about this ( from aufs internal workings point
of view)? Even though it gets "FIXED" on every boot ?

/proc/mounts contents are:

/dev/hda1   /            ext3   rw,data=ordered 0 0
/dev/hda2   /.mount  squashfs ro 0 0
/sysroot/tmp   /tmp   tmpfs  rw 0 0
/sysroot/bin     /bin    aufs
rw,si=db7bc7c0,xino=/tmp/xino,br:/bin=rw:/.mount/bin=ro  0  0
[...]



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

Reply via email to