Le 2001-10-25, BSD User écrivait :
On Wed, 24 Oct 2001, Paul van der Zwan wrote:
I have looked at a trace I made using snoop and it shows an NFS_ACL call which
[...]
It looks like an implementation error in the -current NFS server.
I have been digging at traces of 4.4-RELEASE (which works)
In message [EMAIL PROTECTED], BSD User writes:
Actually, upon instrumenting some code, it looks like RELEASE-4.4 gets it
mostly right. It ejects a PROG_UNAVAIL call which causes the Solaris 8
client to back off. The correct message would seem to be PROC_UNAVAIL,
but I would take PROG_UNAVAIL if
Le 2001-10-25, Ian Dowse écrivait :
I think PROG_UNAVAIL is correct; the packet trace that Thomas
provided shows an RPC request with a program ID of 100227 which is
not the NFS program ID.
Yep. (Incidentally 100227 appears in /etc/rpc as 'nfs_acl').
Try the patch below.
Seems to work.
In message [EMAIL PROTECTED], BSD User wrote:
Actually, upon instrumenting some code, it looks like RELEASE-4.4 gets it
mostly right. It ejects a PROG_UNAVAIL call which causes the Solaris 8
client to back off. The correct message would seem to be PROC_UNAVAIL,
but I would take PROG_UNAVAIL if
On Thu, 25 Oct 2001, Ian Dowse wrote:
I think PROG_UNAVAIL is correct; the packet trace that Thomas
provided shows an RPC request with a program ID of 100227 which is
not the NFS program ID.
I stand corrected. It does indeed attempt to access a different program.
Try the patch below.
In message [EMAIL PROTECTED], Thomas Quinot wrote:
Le 2001-10-14, Paul van der Zwan écrivait :
I am using -current box as a homedir server for my Solaris clients and
have noticed a wierd problem.
Other problems here, with Solaris 2.[68] as clients, and -CURRENT of
yesterday as server. ls
On Wed, 24 Oct 2001, Paul van der Zwan wrote:
I have looked at a trace I made using snoop and it shows an NFS_ACL call which
is not supported by FreeBSD. It should have sent a reply that it does not
know the NFS_ACL protocol but apparently it does not.
The only return traffic I see is an
Le 2001-10-14, Paul van der Zwan écrivait :
I am using -current box as a homedir server for my Solaris clients and
have noticed a wierd problem.
Other problems here, with Solaris 2.[68] as clients, and -CURRENT of
yesterday as server. ls works, but ls -l issues a 'NFS getacl failed'
message
I am using -current box as a homedir server for my Solaris clients and
have noticed a wierd problem.
When I login my homedir gets mounted ok but when I type ls -l it just
waits until I ^C it.
If I run snoop on Solaris I see a getattr request being sent and
an answer being received but apparently
Paul van der Zwan wrote:
If I run snoop on Solaris I see a getattr request being sent and
an answer being received but apparently it gets ignored by Solaris.
This happens on both Sol x86 and Sparc ( both with MU5 installed)
Please do a tcpdump, and examine it; I suspect you will find
that
Actually, I've also noticed problems in FreeBSD-current also- ls and
reads work, but things like mkdir hang. Here's the tcpdump output:
Script started on Sun Oct 14 12:21:50 2001
quarm.feral.com root tcpdump -vv -i fxp0 host antares
tcpdump: listening on fxp0
12:21:58.498568
Hi,
One more problem is in nfsd, if I set it to use udp only it starts
eating all cpu cycles it can get,but only the master process. Trussing
the process shows no system calls whatsoever being performed.
The last one is a know problem. There is a (unfinished) patch available to
solve this
The last one is a know problem. There is a (unfinished) patch available to
solve this problem. Thomas Moestl [EMAIL PROTECTED] is still working on
some issues of the patch. Please contact him if you like to know more.
Here is the URL for the patch:
On Sun, 2001/10/14 at 21:38:26 +0100, Ian Dowse wrote:
The last one is a know problem. There is a (unfinished) patch available to
solve this problem. Thomas Moestl [EMAIL PROTECTED] is still working on
some issues of the patch. Please contact him if you like to know more.
Here is the URL
14 matches
Mail list logo
