https://bugzilla.novell.com/show_bug.cgi?id=344935 Mark Gordon changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |mtgordon@novell.com AssignedTo|bnc-team-screening@forge.provo.novell.com |kernel-maintainers@forge.provo.novell.com Component|Network |Kernel -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

https://bugzilla.novell.com/show_bug.cgi?id=344935#c1 Neil Brown changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |NEEDINFO Info Provider| |kil@systema.ru --- Comment #1 from Neil Brown 2007-12-02 17:31:33 MST --- Would it be possible to get a network trace of the NFS packet. On the client, run tcpdump -w /tmp/dump -s 0 host alpha2 then while that is running, mount the directory and try to access it. Then interrupt the 'tcpdump' and attach the "/tmp/dump" file that was created. Thanks, -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

https://bugzilla.novell.com/show_bug.cgi?id=344935#c3 --- Comment #3 from Igor Klechkovsky 2007-12-03 01:30:15 MST --- Created an attachment (id=185587) --> (https://bugzilla.novell.com/attachment.cgi?id=185587) tcpdump -w /tmp/dump1 -s 0 host alpha2 -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

https://bugzilla.novell.com/show_bug.cgi?id=344935#c5 Igor Klechkovsky changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEEDINFO |NEW Info Provider|kil@systema.ru | --- Comment #5 from Igor Klechkovsky 2007-12-03 01:38:56 MST --- News: "cd" works without "ls" before first "cd". # tcpdump -w /tmp/dump0 -s 0 host alpha2 h505-3:~ # mount alpha2:/usr1/suse /mnt h505-3:~ # cd /mnt h505-3:/mnt # ls 10.2 10.3 h505-3:/mnt # cd 10.3 -bash: cd: 10.3: Not a directory # tcpdump -w /tmp/dump1 -s 0 host alpha2 h505-3:/ # mount alpha2:/usr1/suse /mnt h505-3:/ # cd /mnt h505-3:/mnt # cd 10.3 h505-3:/mnt/10.3 # ls non-oss oss other packman src-oss update vlc h505-3:/mnt/10.3 # cd .. h505-3:/mnt # ls 10.2 10.3 h505-3:/mnt # cd 10.3 h505-3:/mnt/10.3 # # tcpdump -w /tmp/dump2 -s 0 host alpha2 h505-3:~ # mount alpha2:/usr1/suse /mnt h505-3:~ # cd /mnt h505-3:/mnt # cd 10.3 h505-3:/mnt/10.3 # ls non-oss oss other packman src-oss update vlc h505-3:/mnt/10.3 # cd oss -bash: cd: oss: Not a directory -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

https://bugzilla.novell.com/show_bug.cgi?id=344935 User kil@systema.ru added comment https://bugzilla.novell.com/show_bug.cgi?id=344935#c7 --- Comment #7 from Igor Klechkovsky 2007-12-17 00:52:07 MST --- Created an attachment (id=187803) --> (https://bugzilla.novell.com/attachment.cgi?id=187803) corresponds the dump0 -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

https://bugzilla.novell.com/show_bug.cgi?id=344935 User nfbrown@novell.com added comment https://bugzilla.novell.com/show_bug.cgi?id=344935#c9 Neil Brown changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |NEEDINFO Info Provider| |kil@systema.ru --- Comment #9 from Neil Brown 2007-12-17 15:57:32 MST --- Thanks. That helped a lot. It appears that your Tru64 server is returning bad replies to READDIRPLUS. If you run tshark -V -r dump0 | grep fsid to decode the NFS requests and replies and look at the 'fsid' field in each reply you will notice that they are not all the same. Some are fsid: 0x00000000e98632ee others are fsid: 0xffffffffe98632ee The ones with leading zeros are all in response to READDIRPLUS requests. This is clearly an error on the part of the server. Fortunately you can ask the Linux client not to use READDIRPLUS for exactly this sort of reason. If you mount the filesystem with "nordirplus", e.g. mount -o nordirplus alpha2:/usr1/suse /mnt then READDIR will be used instead of READDIRPLUS and it should work better. Please test and report. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

https://bugzilla.novell.com/show_bug.cgi?id=344935 User nfbrown@novell.com added comment https://bugzilla.novell.com/show_bug.cgi?id=344935#c11 Neil Brown changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |RESOLVED Resolution| |INVALID --- Comment #11 from Neil Brown 2008-01-02 15:42:18 MST --- I don't think this is a kernel error, just that different implementations or different operation sequences respond differently to erroneous behaviour by the server. In the "ls;cd" versus "cd;ls" case, the first fsid that Linux will see for a given file will come from READDIRPLUS in the first case, and from GETATTR in the second. As it makes significant use of this value, it will perform badly in the first case where the fsid is wrong, and better in the second case where the first fsid seen is correct. Similarly the Solaris/Linux different is due to handling the value in different way. And yes, the fsid of a particular object should always be the same. It should not change over time and should not change depending on which request is used to retrieve it. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.