OK, I've been searching the archives and google with little luck... I have a directory which needs to be shared with a number of UNIX clients via NFS and with Windows clients via Samba. What is the best way to do this? Should I configure Samba to share the actual NFS mount? Or should I configure Samba to share the actual filesystem directory? Reason I ask, we were using the former method (sharing the NFS mount) and Windows users were complaining about flaky Samba shares. Thanks! Mike
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1> OK, I've been searching the archives and google with little luck... > > I have a directory which needs to be shared with a number of UNIX > clients via NFS and with Windows clients via Samba. What is the best > way to do this? Should I configure Samba to share the actual NFS mount? > Or should I configure Samba to share the actual filesystem directory? > > Reason I ask, we were using the former method (sharing the NFS mount) > and Windows users were complaining about flaky Samba shares.I think you should have your Samba daemon running on the same machine as the NFS daemon. If you do it the other way, then you have two different points of latency for file retrieval for the Samba downloads. Furthermore, what will happen if you have to take down either Samba or NFS for maintenance? This way they need not both be down. For larger systems you might consider having an SCSI hard drive with two ports so that you can access it from two different machine's busses. One machine could run Samba and the other NFS. For even larger storage solutions, think "Network Attached Storage" with a gigabit or fiber backbone and possibly Balancing Domain Controllers. Jim C. -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.5 (MingW32) Comment: Using GnuPG with Thunderbird - http://enigmail.mozdev.org iD8DBQFClALrB4AhF6wVFMERAghWAKCBLIjWP3aNCGQ2PueV29QB/Lnx7ACfS2dn kGSrYgOljPo03YYPo2BhtME=JG87 -----END PGP SIGNATURE-----
>OK, I've been searching the archives and google with little luck... > >I have a directory which needs to be shared with a number of UNIX >clients via NFS and with Windows clients via Samba. What is the best >way to do this? Should I configure Samba to share the actual NFS mount? > Or should I configure Samba to share the actual filesystem directory? > >Reason I ask, we were using the former method (sharing the NFS mount) >and Windows users were complaining about flaky Samba shares.Interesting, My current layout is a Linux server running RH 7.1, a new Linux server running FedoraCore 2 (to be updated to 3) and two Windblows boxes (one 98SE and one W2K). The new Linux server will be taking over the duties of the old. In the meantine, the home partition and the website partition are on the new server. The old Linux box Samba servers to the two Windblows boxes, but it mounts the two partitions via NFS. I never reconfigured the Samba server after I moved the data from those two directories to the new server. Samba happily serves up the local and NFS files without a wimper. The Windoze boxes have never complained. My transfer speed has never had a problem and I not seen a hiccup. Of course, my little home network doesn't have the traffic that you do, so your mileage will probably vary. The point is that Samba will happily share a NFS mount. But, if I read what you have for a configuration, the server is your Samba server box and the NFS server box. Samba can't serve a NFS mounted file when it isn't mounted locally. In your case, you'll NFS export the directory to the Unix boxes and Samba share the same directory to the Windblows boxes. That is basically what we do at work with a whole bunch more Unix boxes and Windblows boxes. Did I understand you setup correctly? MB -- e-mail: vidiot@vidiot.com /~\ The ASCII \ / Ribbon Campaign [So it's true, scythe matters. Willow 5/12/03] X Against Visit - URL: http://vidiot.com/ / \ HTML Email
True, would be good to share both SMB and NFS from the same server. However, there is a possible reason to use SMB from NFS client mount point: Win clients cannot mount SMB shares of two different user names on the same box. I.E., from a Win box I cannot do: net use \\serverA\home /user:Adomain\john net use \\serverA\lab /user:Adomain\labmanager In my case, 'home' and 'lab' files were historically in different Win domains anyway, so I moved on to a work-around to the above, where I NFS mount the 'lab' files from serverA in Adomain to server B in a different domain, and I can do: net use \\serverA\home /user:Adomain\john net use \\serverB\lab /user:Bdomain\labmanager I have a small subset of users in both A Bdomain, so the accounts management is not too cumbersome. Perhaps there are more elegant solutions though, serving all from the same SMB+NFS box. Will look at some of the suggestions as to how to get SMB from NFS mount to work again now with Samba 3 -Ben Ransom>I think you should have your Samba daemon running on the same machine as >the NFS daemon. If you do it the other way, then you have two different >points of latency for file retrieval for the Samba downloads. >Furthermore, what will happen if you have to take down either Samba or >NFS for maintenance? This way they need not both be down. > >For larger systems you might consider having an SCSI hard drive with two >ports so that you can access it from two different machine's busses. >One machine could run Samba and the other NFS. For even larger storage >solutions, think "Network Attached Storage" with a gigabit or fiber >backbone and possibly Balancing Domain Controllers. > > >Jim C. >-----BEGIN PGP SIGNATURE----- >Version: GnuPG v1.2.5 (MingW32) >Comment: Using GnuPG with Thunderbird - http://enigmail.mozdev.org > >iD8DBQFClALrB4AhF6wVFMERAghWAKCBLIjWP3aNCGQ2PueV29QB/Lnx7ACfS2dn >kGSrYgOljPo03YYPo2BhtME>=JG87 >-----END PGP SIGNATURE----- > >-- >To unsubscribe from this list go to the following URL and read the >instructions: https://lists.samba.org/mailman/listinfo/samba