Dear Junjiro, On Thursday 14 January 2010, 04:27:14 sf...@users.sourceforge.net wrote: > Hi Hans, > > "Hans-Peter Jansen": > > for aufs2, I tried these mount variants: > > > > mount -t aufs -o br:/rwroot=rw:/roroot=ro none /root > > resulted in: > > aufs au_xino_create:659:mount[206]: xino doesn't support > > /tmp/.aufs.xino(rootfs) > > > > mount -t aufs -o br:/rwroot=rw:/roroot=ro,xino=/rwroot/.aufs.xino none > > /root resulted in: > > aufs au_xino_create:659:mount[206]: xino doesn't support > > /rwroot/.aufs.xino(nfs) > > > > mount -t aufs -o br:/rwroot=rw:/roroot=ro,noxino none /root > > resulted in: > > aufs au_opts_mount:1456:mount[206]: no branches > > > > So far, I'm unable to use aufs2 in my setup, which is a real pity. > > > > Given, that tmpfs seems to be unable to carry the xino file, and so > > does nfs, how is a NFS3 diskless setup supposed to work now? > > > > Do you have any ideas or recommendations on how to precede? > > Some filesystems doesn't have the neccessary features for aufs XINO > files, and aufs rejects them. > For rootfs (in your first example), you MAY be able to put XINO on it if > you enable AUFS_BR_RAMFS. > For nfs (the second example), aufs doesn't support XINO on nfs. > For tmpfs, it is supported. Try xino=/your/tmpfs/file/path option. > For your last example (noxino), it should work. I don't know why it > failed. Will you try it again?
Okay, here we go. I'm preparing the client setup with kiwi now, and based it on openSUSE 11.1. Since I try to use it out of the box (SuSE still carries a heavily patched kernel..), I'm down to: - kernel 2.6.27.42 - aufs 20081020 Yes, still a overly old aufs in the equation (sorry about that), but one, that is strongly exercised (at least with local filesystems). I adjusted the kiwi initrd in a way, that two nfs3 mounts are unioned, where the xino mapping file resides on tmpfs. The problem is: during initrd, all is well, but after transition to the real root, the aufs / fs is magically turned ro behind the scenes. The same happens, if the rw part is located on tmpfs as well. cat /proc/mounts from initrd: rootfs / rootfs rw 0 0 udev /dev tmpfs rw,mode=755 0 0 172.16.23.110:/work/dlbase/tmp/kde3-tmp /read-only nfs ro,vers=3,rsize=524288,wsize=524288,namlen=255,hard,nointr,nolock ,proto=tcp,timeo=600,retrans=2,sec=sys,mountaddr=172.16.23.110,mountvers=3,mountproto=udp,addr=172.16.23.110 0 0 tmpfs /read-write tmpfs rw 0 0 tmpfs /xino tmpfs rw 0 0 aufs / aufs rw,si=5eed080e,xino=/xino/.aufs.xino,br:/read-write=rw:/read-only=ro 0 0 /proc /proc proc rw 0 0 cat /proc/mounts from first init script: rootfs / rootfs rw 0 0 udev /dev tmpfs rw,mode=755 0 0 172.16.23.110:/work/dlbase/tmp/kde3-tmp /read-only nfs ro,vers=3,rsize=524288,wsize=524288,namlen=255,hard,nointr,nolock ,proto=tcp,timeo=600,retrans=2,sec=sys,mountaddr=172.16.23.110,mountvers=3,mountproto=udp,addr=172.16.23.110 0 0 tmpfs /read-write tmpfs rw 0 0 tmpfs /xino tmpfs rw 0 0 aufs / aufs ro,si=48d0767e,xino=/xino/.aufs.xino,br:/read-write=rw:/read-only=ro 0 0 /proc /proc proc rw 0 0 sysfs /sys sysfs rw 0 0 devpts /dev/pts devpts rw,mode=600 0 0 No error message, no other hint from this switch. Does this rings a bell for you? BTW, I already tried to port the last aufs 1 version to this kernel, but that resulted in segfaults (probably, I missed to adjust some modification between 20081020 and 20090126). Today, I will try to tackle the aufs2 version, but that's going to be even tougher, but at least, we do not commit necrophilia then.. Cordially yours, Pete ------------------------------------------------------------------------------ The Planet: dedicated and managed hosting, cloud storage, colocation Stay online with enterprise data centers and the best network in the business Choose flexible plans and management services without long-term contracts Personal 24x7 support from experience hosting pros just a phone call away. http://p.sf.net/sfu/theplanet-com
