NFS server bug - can someone submit a support request

[Harry Edmon]

Can someone with a support contract submit the bug in NFS Server for Tru64Unix (through 5.1B-4) that is causing problems when mounting on recent Linux kernels? For details, go to:

http://marc.info/?l=linux-nfs&m=117312696519433&w=2

Here is a summary:

The problem is this: Tru64 server exporting Advfs fileystems
return sign extend fsids in most but not all NFS procedures.

Meaning most fattrs returned by the server have a fsid of:
fsid: 0xffffffff8419f8d5

but in some procs (like READDIRPLUS) the fsid is
fsid: 0x000000008419f8d5

Which is _clearly_ wrong and does not happen with UFS
exports on the same server.

So its my contention that Tru64 has been broken forever
since only Linux clients fail, which started due to the
following patch that went into 2.6.12:

commit 55a975937d40cac582e981ddc8ed783b3dcc043c
Author: Trond Myklebust
Date: Fri Jun 9 09:34:19 2006 -0400

NFS: Ensure the client submounts, when it crosses a server mountpoint.

In this patch, fsids are compared to the first fsid that was received
during the mount ...

[Steven Schweda]

You could try:

http://h30097.www3.hp.com/comments.html

It's cheap, anyway, and you never know until
you try.

[Vivek Verma · Accepted solution]

An internal bug report is already filed and
the problem identified.

[Harry Edmon]

Any timeframe for a fix? I really need this ASAP.

[Al Licause]

It would seem that this has been recognized by the maintenance engineering group and is on their list as something to fix. As such it will more than likely appear in the next major patch kit.

Since patch kit 6 was recently released, you may have quite a wait until the next one is available.

Point patches are usually made for customers with support contracts. And it usually requires an elevation to get such patches on a case by case basis.

This is one of the advantages of having a service contract.