Re: OSX NFS-Server FreeBSD NFS Client

2008-01-08 Thread Chuck Swiger

On Jan 7, 2008, at 11:01 PM, Konrad Heuer wrote:
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.



While I certainly wish you the best of luck, previous experience  
suggests that the drawbacks to this approach include not functioning  
properly.


NFS is a stateless protocol, except insofar as rpc.lockd in theory  
provides lockf/flock style locking over the network-- yet Samba/CIFS  
wants to allow extensive use of client side opportunistic locking,  
which means that Samba really, really wants to run off of a local  
filesystem.


--
-Chuck

___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to [EMAIL PROTECTED]


Re: OSX NFS-Server FreeBSD NFS Client

2008-01-08 Thread Konrad Heuer


On Tue, 8 Jan 2008, Chuck Swiger wrote:

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.


While I certainly wish you the best of luck, previous experience suggests 
that the drawbacks to this approach include not functioning properly.


NFS is a stateless protocol, except insofar as rpc.lockd in theory provides 
lockf/flock style locking over the network-- yet Samba/CIFS wants to allow 
extensive use of client side opportunistic locking, which means that Samba 
really, really wants to run off of a local filesystem.


Yes, I agree, locking is a serious problem. The whole thing runs with 
Linux NFS servers for a couple of month now (though I want to migrate to 
OSX NFS servers), and I introduced fake oplocks = yes in smb.conf some 
month ago (which obviously improved stability) and did also some 
experimenting with the -L-option of mount_nfs.


Thank you very much for reply!

Best regards

Konrad Heuer
GWDG, Am Fassberg, 37077 Goettingen, Germany, [EMAIL PROTECTED]

___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to [EMAIL PROTECTED]


Re: OSX NFS-Server FreeBSD NFS Client

2008-01-07 Thread Chuck Swiger

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.


--
-Chuck

___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to [EMAIL PROTECTED]


Re: OSX NFS-Server FreeBSD NFS Client

2008-01-07 Thread Konrad Heuer


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, [EMAIL PROTECTED]


___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to [EMAIL PROTECTED]


OSX NFS-Server FreeBSD NFS Client

2008-01-02 Thread Konrad Heuer


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.


After exporting and mounting, everything seems to work well. But when the 
system gets under some real life load, NFS-mounted file systems begin 
sporadically to hang on the FreeBSD clients without any error message.


On the NFS clients, although some processes are blocked in kernel mode 
when accessing files, others still can work successfully. But with 
increasing time, the situation becomes worse and worse until we have to 
restart the operating system by ungently switching the power off and on 
again.


The OS X server seems to be unimpressed by all this.

I'd greatly appreciate any hint or idea what to do. Of course, I did some 
experimenting with NFS mount options (-rsize,-wsize,-L), but got no 
improvement.


Best regards

Konrad Heuer
GWDG, Am Fassberg, 37077 Goettingen, Germany, [EMAIL PROTECTED]
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to [EMAIL PROTECTED]