> -----Original Message----- > From: linux-nfs-owner@xxxxxxxxxxxxxxx [mailto:linux-nfs- > owner@xxxxxxxxxxxxxxx] On Behalf Of Sven Geggus > Sent: Friday, February 15, 2013 4:38 AM > To: linux-nfs@xxxxxxxxxxxxxxx > 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 > If your applications are unable to cope with 64-bit inode numbers, then you can turn back on the inode number mapping on the nfs client: echo "options nfs enable_ino64=N" >/etc/modprobe.d/options-local.conf and then either reboot, or unload and reload your nfs module. Trond ��.n��������+%������w��{.n�����{��w��� jg��� �����ݢj����G���� ���j:+v���w�m������w�������h�����٥
