Date: Tue, 8 Jan 2008 08:01:28 +0100 (CET) From: Konrad Heuer <kheuer2@gwdg.de> To: Chuck Swiger <cswiger@mac.com> Cc: freebsd-questions@freebsd.org Subject: Re: OSX NFS-Server && FreeBSD NFS Client Message-ID: <20080108075717.A99137@gwdu60.gwdg.de> In-Reply-To: <872A6988-2C89-4AF1-99E6-57B744C799CB@mac.com> References: <20080103073138.G99137@gwdu60.gwdg.de> <872A6988-2C89-4AF1-99E6-57B744C799CB@mac.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On Mon, 7 Jan 2008, Chuck Swiger wrote: > On Jan 2, 2008, at 10:50 PM, Konrad Heuer wrote: >> I observe a serious problem with NFS exports from a Mac OS X 10.4 server to >> FreeBSD 6.2 NFS clients (itself running on DELL PowerEdge 2850 server >> hardware). >> >> We use the StorNext distributed file system in which FreeBSD cannot >> participate straightly (sorry to say). But OS X can do using the XSAN >> software from Apple, so we integrated the OS X server into the StorNext >> environment. >> >> We want OS X to NFS export the filesystems to FreeBSD clients, which by >> itself for example act as SMB servers using Samba 3.0.x. > > You really don't want to export a filesystem which itself is being mounted > remotely. If you want to provide SMB filesharing for these files, run Samba > on the OS X machine(s) directly. Knowing all the drawbacks including reduced bandwith, there are some important organizational reasons, thus I want to do so. Moreover, Samba ist just one application on the NFS clients, although an important one. Konrad Heuer GWDG, Am Fassberg, 37077 Goettingen, Germany, kheuer2@gwdg.de
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20080108075717.A99137>