Very Computer

We really don't know where to look first.  This happens only in this
particular combination.

The bug affects tcsh's completion mechanism, it's ls-F builtin and all
filename pattern expansions.

helbing.birne ~ > uname -a
SunOS birne 5.6 Generic sun4u sparc SUNW,Ultra-1

helbing.birne ~ > set | grep tcsh
shell   /usr/bin/tcsh
tcsh    6.07.02
version tcsh 6.07.02 (Astron) 1996-10-27 (sparc-sun-solaris) options 8b,nls,dl,rh

helbing.birne vol1/scratch/bla > df -k .
Filesystem            kbytes    used   avail capacity  Mounted on
loriot:/export/vol1  9056352 4262344 4794008    48%    /net/loriot/export/vol1

helbing.birne vol1/scratch/bla > ls -l
total 0
-rw-r--r--   1 helbing  finstud        0 Feb 27 14:15 file
-rw-r--r--   1 helbing  finstud        0 Feb 27 14:15 file.1
-rw-r--r--   1 helbing  finstud        0 Feb 27 14:15 file.2

helbing.birne vol1/scratch/bla > ls-F

helbing.birne vol1/scratch/bla > ls *
ls: No match.

helbing.loriot ~ > uname -a
IRIX64 loriot 6.4 02121744 IP27

helbing.loriot vol1/scratch/bla > df -k .
Filesystem             Type  kbytes     use     avail  %use Mounted on
/dev/xlv/home           xfs  9056352  4262064  4794288  48  /export/vol1

What do I have to do to fix this?

Ralf
--
"Ever get pieces of flesh caught in your teeth?  I *hate* that!"

Ralf Helbing,    University of Magdeburg,     Department of Computer Science
39106 Magdeburg, UniPlatz 2, G 223                  Phone: +49 0391 67-12189

[[ PLEASE DON'T SEND ME EMAIL COPIES OF POSTINGS ]]

This is, in fact, a known bug in Solaris 2.6 when interacting with IRIX 6.x,
even when you specify -32bitclients on share (you must use that export option
anyway).

The symptoms you see should go away when you compile tcsh for "large files",
but other applications still work.

It's an actual bug, at first thought only to be a library bug, but it turns
out there's also a problem in the NFSv2 code.

If you're content using NFSv3 only to communicate with the SGI (and I know
some people don't like to say "NFS V3 and SGI" in one sentence because of
past problems), then th elatest libc patch for 2.6 should work (but it
will break NFSv2 which needs a separate kernel patch)

Casper

--
Expressed in this posting are my opinions.  They are in no way related
to opinions held by my employer, Sun Microsystems.
Statements on Sun products included here are not gospel and may
be fiction rather than truth.

Quote:

>We really don't know where to look first.  This happens only in this
>particular combination.
>...
>What do I have to do to fix this?

Sun have only very recently found the cause of the problem where Solaris 2.6
would really only accept 31 bit NFS cookies. To fix the problem you need
patch 105210-02 (and 105926-01 for a new statically linked tar), and
a kernel patch which hasn't been released yet. You might be able to get
something out of them by mentioning escalation number 512865.

In the meantime you should be able to avoid the problem by using NFS v2,
WITHOUT installing patch 105210-02. Using NFS v3 WITH patch 105210-02
should also work.