Subject: Re: Netatalk and NFS
From: Darron Froese (darron@froese.org)
Date: Wed Jan 10 2001 - 00:17:21 EST
on 1/8/01 8:29 AM, Matthew Keller at kellermg@potsdam.edu wrote:
> Make sure your time on both NFS server and NFS client are the same-
> Down to the second.
Check. I just synched them with ntpdate to the same server.
> I use the following flags when I mount NFS volumes
> for share with Netatalk. You gotta turn off NFS locking because Apple is
> lame and is CONSTANTLY writing and reading resource forks while a file
> is open (even in the midst of a copy)
>
> nolock,nosuid,noexec,wsize=8192,bg,nodev,rsize=8192,intr
I've got this:
soft,intr,user,nolock,nosuid,noexec,nodev,wsize=8192,rsize=8192
I can now read just fine from those NFS shared directories, but I cannot
write reliably. I am able to write a file once in a while - but not on
command.
Usually I get "The item $ITEM cannot be written because of an error of type
-50. Would you like to continue?" Of course continuing does nothing.
I have found a workaround for the time being - I can copy the file to a
non-NFS mounted directory and then *move* it to the NFS mounted directory.
The file is fine when I copy it off of the NFS server (via an additional
test netatalk server).
Any other ideas?
-- Darron darron@froese.org
This archive was generated by hypermail 2b28 : Sun Oct 14 2001 - 03:04:30 EDT