NFS4: "Value too large for defined data type" problem

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



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
--
To unsubscribe from this list: send the line "unsubscribe linux-nfs" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html


[Index of Archives]     [Linux Filesystem Development]     [Linux USB Development]     [Linux Media Development]     [Video for Linux]     [Linux NILFS]     [Linux Audio Users]     [Yosemite Info]     [Linux SCSI]

  Powered by Linux