Hello
I read your thread about problem with NFS v3.
I encountered this kind of problem some times ago (since FreeBSD 2.2.2)
between DEC stations running Digital Unix 3.2 ou 4.0.
When doing "ls" in a NFS mounted directory, I got something like that :
# mount -t nfs -o nfsv3
We have a number of solaris 2.78 machines (I am in the process of installing
them now), and I notice that if I ls a directory that is mounted NFSv3/UDP from
a FreeBSD server to a Solaris 2.7 client there are a number of files that
show up missing. This is most intreaging with a large
"David E. Cross" wrote:
Count me as one of the ones who do not accept this answer. I realize that
It was not the "answer" which was not accepted. Someone actually
argued it could not be an NFS protocol bug because the Solaris stack
was the reference implementation, ergo it does not have
:As I recall, we had two alternatives. First, knowingly not comply to
:the spec, because Solaris doesn't handle it. Second, change the way
:we read directories so we can avoid doing things in the way Solaris
:can't handle. The latter is a very sore spot, and not trivial.
:
:I was under the
We have a number of solaris 2.78 machines (I am in the process of installing
them now), and I notice that if I ls a directory that is mounted NFSv3/UDP from
a FreeBSD server to a Solaris 2.7 client there are a number of files that
show up missing. This is most intreaging with a large untar as I
"David E. Cross" wrote:
We have a number of solaris 2.78 machines (I am in the process of installing
them now), and I notice that if I ls a directory that is mounted NFSv3/UDP from
a FreeBSD server to a Solaris 2.7 client there are a number of files that
show up missing. This is most
6 matches
Mail list logo
