>On Fri, Feb 6, 2009 at 6:38 PM, <sf...@users.sourceforge.net> wrote: [...] > >> Secondly, since the nash shell mount was not accepting 'none' for a device >> name, >> I tried the following (on the lines of the above mount already present >> therein): >> >> mount -o br:/sysroot/bin:/sysroot/.mount/bin=ro -t aufs /sysroot/bin >> /sysroot/bin >> >> and got the following error: >> >> aufs test_br:283:init[1]: write permission for readonly fs or inode, >> /sysroot/bin >> mount: error mounting /sysroot/bin on /sysroot/bin as aufs: Invalid argument >> >> >> Am I doing it correctly ? > > Yes, if I were you I would try the same command. And the error message > shows that we made one step forward I think. > It says the first branch "/sysroot/bin" is readonly, so you cannot mount > aufs as read/write. Actually /sysroot was mounted readonly. > ---------------------------------------------------------------------- > echo Creating root devices > mkrootdev -t ext3 -o ro /dev/hda1 > echo Mounting root filesystem > mount --ro -t ext3 /dev/hda1 /sysroot > ::: > ---------------------------------------------------------------------- > > If you want to use /sysroot/bin as a writable branch of aufs, then you > need to remove "--ro" at mounting /sysroot. > [...] > > J. R. Okajima >
Hi Junjiro, I removed the --ro, while mounting /sysroot . and then the mount was successful, but I encountered another issue thereafter; The way RHEL is designed that initially the root filesystem ( / ) is mounted read-only and later, when init starts executing, it reads /etc/fstab and tried to run fsck , and thereafter remount it( root filesystem - / ) read-write. Now, the init complains that it cannot run fsck on a 'mounted' root filesystem. So, I tried to change the strategy a bit: 1.mount /sysroot read-only as before. 2.change aufs mount as follows: mount -t aufs -o br:/sysroot/bin=ro:/sysroot/.mount/bin=ro /sysroot/bin /sysroot/bin 3.edit the /etc/fstab so that now init re-mounts aufs as well as root fs as rw I tried step 2 with my running CentOS, it worked , albeit with a warning in dmesg: aufs verify_opts:1267:mount[7065]: first branch should be rw (One ancillary query: Can we merge two read-only branches as a read-only union ? ) However, in the initrd boot o/p the aufs mount fails as follows: aufs au_xino_create:512:init[1]: open /tmp/.aufs.xino(-2) mount: error mounting /sysroot/bin on /sysroot/bin as aufs: Invalid argument Why am I getting failure on boot time, but not otherwise ? 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
