Am Donnerstag, 7. März 2013, 15:24:40 schrieb Eibo Thieme: > It is embarrassing but I have to admit that I had not gotten the moment > of the error right. Sorry for having you look in the wrong direction. > > The error will trigger even earlier, and I seem to have found the exact > prerequisites for it. I could provoke the error with: > > mount -t nfs -o rw,nolock 192.168.0.1:/export/hti13 /aufs/private > mount -t nfs -o ro,nolock 192.168.0.1:/export/ /aufs/server > > mount -t aufs -o noxino,dirs=/aufs/private=rw:/aufs/server=ro none /root >
It's probably just me, but mounting the rw tree as part (subtree) of the ro tree is looking strange, and *might* trigger some entanglements in NFS machinery. JFYI, in my diskless setups I use separate trees, a tmpfs for stable inodes (xino), and additionally the udba=reval option: stability trumps maximum speed settings. Cheers, Pete ------------------------------------------------------------------------------ Everyone hates slow websites. So do we. Make your web apps faster with AppDynamics Download AppDynamics Lite for free today: http://p.sf.net/sfu/appdyn_d2d_mar
