2013-02-15 09:38:00

by Sven Geggus

[permalink] [raw]
Subject: NFS4: "Value too large for defined data type" problem

Hello,

is there something which can be done server-side to work around the "Value
too large for defined data type" problem with huge inode Numbers?

First of all, I'm not shure if this is an NFS problem or one of the
underlying filesystem.

Background:
I set up a new NFS-server (NFS4) recently. The server works fine so far with
64 bit Linux clients.

It also mostly works with 32 bit Linux clients when either the stat system
call is not used or "-D_FILE_OFFSET_BITS=64" has been used.

This is because on 32 bit Linux ino_t is not 64-bit otherwise.

Unfortunately at least the 32bit Version of Debian stable (6.0) seems to
break all over the place. E.g. in gnome when stat ~/.gnome2_private/ fails
it is assumed that the directory has to be created which will of course make
the subsequent call to mkdir also fail and break the whole desktop
environment afterwords.

Regards

Sven

--
Um Kontrolle Ihres Kontos wiederzugewinnen, klicken Sie bitte auf das
Verbindungsgebrüll. (aus einer Ebay fishing Mail)

/me is giggls@ircnet, http://sven.gegg.us/ on the Web


2013-02-15 18:26:29

by Myklebust, Trond

[permalink] [raw]
Subject: RE: NFS4: "Value too large for defined data type" problem

PiAtLS0tLU9yaWdpbmFsIE1lc3NhZ2UtLS0tLQ0KPiBGcm9tOiBsaW51eC1uZnMtb3duZXJAdmdl
ci5rZXJuZWwub3JnIFttYWlsdG86bGludXgtbmZzLQ0KPiBvd25lckB2Z2VyLmtlcm5lbC5vcmdd
IE9uIEJlaGFsZiBPZiBTdmVuIEdlZ2d1cw0KPiBTZW50OiBGcmlkYXksIEZlYnJ1YXJ5IDE1LCAy
MDEzIDQ6MzggQU0NCj4gVG86IGxpbnV4LW5mc0B2Z2VyLmtlcm5lbC5vcmcNCj4gU3ViamVjdDog
TkZTNDogIlZhbHVlIHRvbyBsYXJnZSBmb3IgZGVmaW5lZCBkYXRhIHR5cGUiIHByb2JsZW0NCj4g
DQo+IEhlbGxvLA0KPiANCj4gaXMgdGhlcmUgc29tZXRoaW5nIHdoaWNoIGNhbiBiZSBkb25lIHNl
cnZlci1zaWRlIHRvIHdvcmsgYXJvdW5kIHRoZSAiVmFsdWUNCj4gdG9vIGxhcmdlIGZvciBkZWZp
bmVkIGRhdGEgdHlwZSIgcHJvYmxlbSB3aXRoIGh1Z2UgaW5vZGUgTnVtYmVycz8NCj4gDQo+IEZp
cnN0IG9mIGFsbCwgSSdtIG5vdCBzaHVyZSBpZiB0aGlzIGlzIGFuIE5GUyBwcm9ibGVtIG9yIG9u
ZSBvZiB0aGUgdW5kZXJseWluZw0KPiBmaWxlc3lzdGVtLg0KPiANCj4gQmFja2dyb3VuZDoNCj4g
SSBzZXQgdXAgYSBuZXcgTkZTLXNlcnZlciAoTkZTNCkgcmVjZW50bHkuIFRoZSBzZXJ2ZXIgd29y
a3MgZmluZSBzbyBmYXIgd2l0aA0KPiA2NCBiaXQgTGludXggY2xpZW50cy4NCj4gDQo+IEl0IGFs
c28gbW9zdGx5IHdvcmtzIHdpdGggMzIgYml0IExpbnV4IGNsaWVudHMgd2hlbiBlaXRoZXIgdGhl
IHN0YXQgc3lzdGVtIGNhbGwNCj4gaXMgbm90IHVzZWQgb3IgIi1EX0ZJTEVfT0ZGU0VUX0JJVFM9
NjQiIGhhcyBiZWVuIHVzZWQuDQo+IA0KPiBUaGlzIGlzIGJlY2F1c2Ugb24gMzIgYml0IExpbnV4
IGlub190IGlzIG5vdCA2NC1iaXQgb3RoZXJ3aXNlLg0KPiANCj4gVW5mb3J0dW5hdGVseSBhdCBs
ZWFzdCB0aGUgMzJiaXQgVmVyc2lvbiBvZiBEZWJpYW4gc3RhYmxlICg2LjApIHNlZW1zIHRvDQo+
IGJyZWFrIGFsbCBvdmVyIHRoZSBwbGFjZS4gRS5nLiBpbiBnbm9tZSB3aGVuIHN0YXQgfi8uZ25v
bWUyX3ByaXZhdGUvIGZhaWxzIGl0DQo+IGlzIGFzc3VtZWQgdGhhdCB0aGUgZGlyZWN0b3J5IGhh
cyB0byBiZSBjcmVhdGVkIHdoaWNoIHdpbGwgb2YgY291cnNlIG1ha2UgdGhlDQo+IHN1YnNlcXVl
bnQgY2FsbCB0byBta2RpciBhbHNvIGZhaWwgYW5kIGJyZWFrIHRoZSB3aG9sZSBkZXNrdG9wIGVu
dmlyb25tZW50DQo+IGFmdGVyd29yZHMuDQo+IA0KPiBSZWdhcmRzDQo+IA0KPiBTdmVuDQo+IA0K
DQpJZiB5b3VyIGFwcGxpY2F0aW9ucyBhcmUgdW5hYmxlIHRvIGNvcGUgd2l0aCA2NC1iaXQgaW5v
ZGUgbnVtYmVycywgdGhlbiB5b3UgY2FuIHR1cm4gYmFjayBvbiB0aGUgaW5vZGUgbnVtYmVyIG1h
cHBpbmcgb24gdGhlIG5mcyBjbGllbnQ6DQoNCmVjaG8gIm9wdGlvbnMgbmZzIGVuYWJsZV9pbm82
ND1OIiA+L2V0Yy9tb2Rwcm9iZS5kL29wdGlvbnMtbG9jYWwuY29uZg0KDQphbmQgdGhlbiBlaXRo
ZXIgcmVib290LCBvciB1bmxvYWQgYW5kIHJlbG9hZCB5b3VyIG5mcyBtb2R1bGUuDQpUcm9uZA0K

2013-02-15 18:18:35

by J. Bruce Fields

[permalink] [raw]
Subject: Re: NFS4: "Value too large for defined data type" problem

On Fri, Feb 15, 2013 at 09:37:57AM +0000, Sven Geggus wrote:
> Hello,
>
> is there something which can be done server-side to work around the "Value
> too large for defined data type" problem with huge inode Numbers?
>
> First of all, I'm not shure if this is an NFS problem or one of the
> underlying filesystem.
>
> Background:
> I set up a new NFS-server (NFS4) recently. The server works fine so far with
> 64 bit Linux clients.
>
> It also mostly works with 32 bit Linux clients when either the stat system
> call is not used or "-D_FILE_OFFSET_BITS=64" has been used.
>
> This is because on 32 bit Linux ino_t is not 64-bit otherwise.
>
> Unfortunately at least the 32bit Version of Debian stable (6.0) seems to
> break all over the place. E.g. in gnome when stat ~/.gnome2_private/ fails
> it is assumed that the directory has to be created which will of course make
> the subsequent call to mkdir also fail and break the whole desktop
> environment afterwords.

What filesystem are you exporting?

For xfs, as an example, see the discussion of 64-bit inode numbers in
the mkfs.xfs man page.

--b.