i've been experimenting a bit with reexporting namespaces that have remote elements. sometimes the remote machine goes away. unfortunately when this happens, the first process to wander into the missing mount hangs up everything. it appears that exportfs defends against this; it is designed to fork when it detects it is traversing a mount point (exportsrv.c:652). this test always fails because QTMOUNT is never set. it appears that this bit is always clobbered when being passed up to user space. in tracking that down, i noticed that fixmount traverses the mount point anyway, so QTMOUNT, even if set, would be seen too late.
so should QTMOUNT be removed, or have i missed something? - erik
