Samba on NFS(NFS 에서 삼바사용)

검색은 해봤지만, 딱히 추천할 만한 조합은 아니라고 한다.

NFS is known for having locking problems. That is why it is never used for shared directories. Usually you would mount an NFS directory read only or as a home folder where only one user can open and lock each file. I recommend dropping NFS and using only Samba shares. Samba handles file locking very well and it also has user authentication whereas NFS handles only host based authentication. Plus Windows utilities for NFS are very rare and poor in design. Samba is called The NFS Bloodbath. NFS has litteraly been fazed out by Samba. Another very promissing file sharing method is sshfs which is user based and with high encryption (excellent sharing directories over WAN connections). [링크 : http://www.linuxquestions.org/questions/linux-software-2/samba-on-nfs-file-locking-476005/]

No, it will always be both slower and more dangerous to run Samba on an NFS client.  Slower, because the traffic must traverse 2 network links. More dangerous, because Samba cannot detect NFS access to the files it shares, and therefore Oplocks break. Always run just one file-server, sharing out multiple protocols (if possible). [링크 : http://www.unixresources.net/linux/lf/56/archive/00/00/06/13/61337.html]

아무튼 현재 겪고 있는 증상은,
smbtree 명령을 이용해서 NFS Client에서 네트워크를 검색하면
\\LOCALHOST와 NFS 서버의 이름만 나온다는 점이다.