I have found what I believe to be a bug.
I can reproduce this error on different computers.
I have tried it using different underlining file
systems on the server.
I have tried mounting with the noac option in case it
is an attribute caching problem.
All mounts are also using the nolock option.
Results of running a command is in brackets under the
command.
If I do the following on two clients in a directory
which is mounted on both of them from the server.
Step Client1 Client2
1) create file
2) ls ls
(sees the file) (sees the file)
3) rm file
4) ls ls
(no such file or directory)
(no such file or directory)
5) ln -s ../dir file
6) ls ls
(ls: file: Input/output error)
(sees the file as it should)
I have tested this little problem by creating a normal
file in step 5 instead of a link and everything works
properly.
MArk
Logged In: YES
user_id=573509
I realized the stype I used for the commands is very unreadable.
Hopefully as I'll show them below will be more readable.
Where the command produces output it is show in brackets
after the command.
MArk
1)
Client1> create file
2)
Client1> ls (Sees the file)
Client2> ls (Sees the file)
3)
Client2> rm file
4)
Client1> ls (no such file or directory)
Client2> ls (no such file or directory)
5)
Client1> ln -s ../dir file
6)
Client1> ls (ls: file: Input/output error)
Client2) ls (sees the file as it should)