NFS problem: file doesn't appear in file listing, but can be accessed directly

Markus Gebert markus.gebert at hostpoint.ch
Sat Aug 7 13:11:06 UTC 2010


On 07.08.2010, at 02:35, Rick Macklem wrote:

>> Subject: Re: NFS problem: file doesn't appear in file listing, but can be accessed directly
>> On 03.08.2010, at 16:36, Attila Nagy wrote:
>> 
>>>> You can try replacing the client and server with the experimental
>>>> ones and see if that fixes the problem.
>>>> For the client: mount with "-t newnfs" instead of "-t nfs"
>>>> For the server: start both mountd and nfsd with the "-e" option
>>> Sure. It works with the newnfs client, so it must be either a weird
>>> interaction between the FreeBSD server and client (old), or a client
>>> bug.
>> 
>> Have you tried comparing on-the-wire NFS requests and responses
>> between newnfs and legacy nfs clients for your test case? Maybe you
>> can rule out the former like this. Or at least prove that the server
>> actually responds correctly to the READDIR request.
>> 
> Well, I looked at a packet capture emailed to me by Attila Nagy and
> the filename shows up in the Lookup near the end (the "ls -la"), but
> is not in any of the readdir replies (a search from the start of the
> capture in wireshark only finds it at the Lookup). Therefore, I think
> the problem is w.r.t. the server. (He did this failed case with the
> "newnfs", so both clients see the problem.)


I agree, this must be some kind of server issue then. Still, I wonder why the solaris client didn't show the problem...


Markus




More information about the freebsd-fs mailing list