On Monday 21 October 2024 03:12:23 BST Peter Humphrey wrote: > On Friday 18 October 2024 15:55:19 BST Michael wrote: > > --->8 > > > exportfs -rav > > Ah! I knew about 'exportfs -r' but not the 'av'. When I added that I got > this: > > exportfs: duplicated export entries: > exportfs: > :192.168.178.7(rw,sync,insecure,no_subtree_check,all_squash,anonuid=250,ano > ngid=250) exportfs: > :192.168.178.7(rw,sync,insecure,no_subtree_check,all_squash,anonuid=250,ano > ngid=250) exporting :/mnt/nfs/portage.packages > exporting > :192.168.178.7(rw,sync,insecure,no_subtree_check,all_squash,anonuid=250,ano > ngid=250) exportfs: Failed to stat > 192.168.178.7(rw,sync,insecure,no_subtree_check,all_squash,anonuid=250,anon > gid=250): No such file or directory exporting :/mnt/nfs/portage > exporting :192.168.178.7(rw,sync,no_subtree_check,crossmnt,fsid=0) > exportfs: Failed to stat > 192.168.178.7(rw,sync,no_subtree_check,crossmnt,fsid=0): No such file or > directory > > Of course there's a duplicate export entry; I'm exporting two directories to > the one machine. Well, three actually, counting the top-level one, > /mnt/nfs. But is that duplication the cause of the 'Failed to stat...'? > > Do I need to set some opotions on an rpc service, or something?
Assuming all required directories are on the same fs, what happens if you *only* export the parent directory? Something like this: /mnt/nfs \ 192.168.178.7/32(rw,sync,insecure,no_subtree_check,all_squash,anonuid=250,anongid=250)
signature.asc
Description: This is a digitally signed message part.
