In completing some diskless systems I wanted to each system to use the
servers /tmp file system which is a 4gb tmpfs filesystem. Which I must
say ramdisks in Linux have become very easy to use :)

Now I was already doing some stuff, binding directories, similar to this
example[1], but not using aufs, because I want rw on each workstation.
So I can log into each one, or all and run updates. Even though it
updates a common shared core. More on the diskless systems and stuff
another time.

Anyway I have multiple local directories all bound into one export
directory per system. Which was nice conceptually, one export, but a
kinda nasty fstab. Better than nasty fstab and exportfs. However I ran
into a very annoying problem, that was preventing only the tmpfs bind.

Good rootfs being mounted via nfs
rpc.mountd[2252]: authenticated mount request from 192.168.1.201:853 for 
/ws/ws1/export (/ws/ws1/export)


Bad, /tmp directory, which is tmpfs binded on the server could not be mounted :(

rpc.mountd[2252]: qword_eol: fflush failed: errno 22 (Invalid argument)
rpc.mountd[2252]: Cannot export /ws/ws1/export/tmp, possibly unsupported 
filesystem or fsid= require


Now I could have done a tmpfs per system, and that likely would have
worked right away. But thats not what I wanted, and would waste
resources. I just wanted one big global /tmp tmpfs file system on the
server that has more memory that is ever used. Systems themselves could
use a bit more, thus not doing /tmp on a local tmpfs ramdisk.

Took me a bit to figure out the fix. The fsid thing is some what
telling, but also misleading at the same time. After tons of googling,
no luck at a solution. I finally came across one myself via trial and
error.

/ws/ws1/export          
192.168.1.201(rw,sync,no_root_squash,no_subtree_check,crossmnt,fsid=1)
/ws/ws1/export/tmp      
192.168.1.201(rw,sync,no_root_squash,no_subtree_check,crossmnt,fsid=2)

Its pretty odd, since I am not mounting the /ws/ws1/export/tmp export.
But without that export, and setting the fsid to something other than
the rootfs export, I get the above error. With the dual entries and
single mount of the first export at boot, things work as I wanted.

Seems a bit off to me, but thought I would mention it here. Since I did
not find a solution via Googling and wanted to make note of it for
myself and others.

     1. http://www.gentoo-wiki.info/HOWTO_Gentoo_Diskless_Install

-- 
William L. Thomson Jr.
Obsidian-Studios, Inc.
http://www.obsidian-studios.com


---------------------------------------------------------------------
Archive      http://marc.info/?l=jaxlug-list&r=1&w=2
RSS Feed     http://www.mail-archive.com/[email protected]/maillist.xml
Unsubscribe  [email protected]

Reply via email to