Quoting Steve Dickson (SteveD@xxxxxxxxxx): > > This entire process of reading /etc/mtab 17028 times takes a lot of > > time during which the client stalls, but in the end 'it just works > > fine'. It just takes ages when you try to tab-complete on a client. > Taking a quick look... it appears the only way rpc.mountd will read > /etc/mtab is if the 'crossmnt' export flag is set. Is this the case? Yes. IIRC this was necessary for this situation: Server has filesytems mounted on /mnt/pt1 and /mnt/pt1/foo. Both /mnt/pt1 and /mnt/pt1/foo are exported with 'crossmnt'. Clients that mount just /mnt/pt1 can also reach /mnt/pt1/foo. > > Could someone point me to the code that is involved in doing this? > utils/mountd/cache.c:nfsd_fh():path = next_mnt(&mnt, exp->m_export.e_path); Thanks. I'll dig around some more and see what i can find. -Sndr. -- | What are the little plastic endings on your shoelaces called? | 4096R/20CC6CD2 - 6D40 1A20 B9AA 87D4 84C7 FBD6 F3A9 9442 20CC 6CD2 -- To unsubscribe from this list: send the line "unsubscribe linux-nfs" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
