Generic_118833-17 will contain the fh changes I describe. If the server is running the kernel patch that contains zfs, then it has these changes.
I'll see if I can find an s10 fcs server. In any case, it's broken in snv, so I'll be fixing it there. Nicholas Senedzuk wrote: > Bill, > > I am running S10U1 and having the issue and not S10U2. > > Nick > > On 7/17/06, *Bill Baker* <Bill.Baker at sun.com > <mailto:Bill.Baker at sun.com>> wrote: > > > I've reproduced this failure on snv_43, for both client and > server. The server is failing to decode the file handle from > the client. I have a suspicion that this is being caused by > some fh changes we made to both snv and s10u2 in order for > v3 to support .zfs. > > I've opened bug ID 6449532 to track the problem. > > Thomas Haynes wrote: > > BCC to sysadmin-discuss > > > > Nicholas Senedzuk wrote On 07/14/06 09:20,: > > > >> pos-qa0 is a Solari 10 system. If I don't do the -o vers=3 > everything > >> works > >> fine with the mount. > >> > >> > >> root at pos-qa0# dfshares janus > >> RESOURCE SERVER ACCESS TRANSPORT > >> janus:/cdrom/s10_606_software_companion janus - > - > >> root at pos-qa0# mount -o vers=3 > janus:/cdrom/s10_606_software_companion > >> /mnt > >> nfs mount: mount: /mnt: Stale NFS file handle > >> root at pos-qa0# > >> > >> On 7/13/06, Thomas Haynes < Thomas.Haynes at sun.com > <mailto:Thomas.Haynes at sun.com>> wrote: > >> > >>> > >>> > >>> > >>> Nicholas Senedzuk wrote On 07/13/06 15:40,: > >>> > >>> > I have tried unshareing and reshareing the cdrom several > times and > >>> > that has > >>> > done nothing. Remember I can share the cdrom to another > Solaris 10 > >>> system > >>> > just not anything under Solaris 10. > >>> > > >>> > uname -a from both systems, > >>> > > >>> > SunOS janus 5.10 Generic_118833-17 sun4u sparc SUNW,A70 > >>> > > >>> > SunOS frostbitefalls 5.9 Generic_118558-21 sun4u sparc > >>> SUNW,Sun-Fire-V240 > >>> > > >>> > > >>> >> > >>> > > >>> Filehandles are built differently for NFSv3 and NFSv4. > >>> > >>> Can you mount from another Solaris 10 client while specifying > >>> that vers=3? > >>> > >>> -- > >>> Tom Haynes > >>> tdh at sun.com <mailto:tdh at sun.com> > >>> > >>> > >> > > To recap, fsinfo3 is failing with ESTALE on a share of a CDROM. > > It doesn't matter if the client is Solaris 9 or 10. > > > > Anyone seen this before? > > > >