[Lustre-discuss] NFS problem after upgrade to 1.8.3

[Alexey Lyashkov]

Bernd,

that is problem not related to stack size.
mountd should encode {sb->sb_dev, inode->i_no} in own structure, but for mount v1 sb_dev too short to store full sb_dev (it is 16bit, but nfs fid v1 has 8 for it) bit but lustre client can generate that.
in that case nfsd got invalid NFS fid to client and broken to find correct inode to get attributes and return -ENOENT. in that case ls -l will show "?" instead of real inode attributes.


On Nov 12, 2010, at 15:46, Bernd Schubert wrote:

> Hello Tina,
> 
> On Friday, November 12, 2010, Tina Friedrich wrote:
>> Hello List,
>> 
>> we re-export the file system via NFS for a couple of things. All the
>> re-exporters are Red Hat 5.5 servers running kernel 2.6.18-194.17.1.el5
>> (patchless clients).
> 
> that is your problem. You MUST use a patched version, or least a kernel with 
> 8kB stack size. RHEL5 has 4kB by default, which is not sufficient and 
> therefore in early 1.8 versions a patch landed that disallowed NFS exports.
> 
> 
> Cheers,
> Bernd
> 
> 
> 
> -- 
> Bernd Schubert
> DataDirect Networks
> _______________________________________________
> Lustre-discuss mailing list
> Lustre-discuss at lists.lustre.org
> http://lists.lustre.org/mailman/listinfo/lustre-discuss