Value too large for defined data type error on input thread

[Gene Millard]

We have a input thread setup as PROTOCOL:fileset-local and we get this message.

cannot stat /mnt/NT115/interface_prod/interface_out/Epic_op_time_item: Value too large for defined data type

The file is there but is not being sent to the outbound thread.

Any suggestions?

Gene

The Guthrie Clinic
Sayre, PA

Topic

[Marc Pleijers]

Hi Gene,

The problem you report sounds familiar. We had the same issue over here.

The server you mount to is probably a windows server.

The problem is caused by the way you have created the mount.

The correct way to create a mount is:

mount -t cifs -o user=me,pass=secret,nounix,noserverino //server/share /mount

Especially the two parameters nounix and noserverino are important and will fix the problem.

The fault: Cannot stat : Value too large for defined data type

is caused by the missing parameter noserverino

This parameter deals with inodes. An inode is a way to store files on a disk. the name comes from index-node. Large files are divided and stored in small pieces called sectors. Administration is necessary to know which sector is belongs to which file.

When you mount to a system that uses a 64 bit OS that system returns a 64 bit inode ID to Cloverleaf as a reference to the file. Cloverleaf however is still 32 bit. Cloverleaf tries to store that 64 bit reference in a 32 bit buffer which does not fit and results in an Value too large for this data type error.

With the option noserverino you state that you don’t want to use the inode ID of the server when dealing with the mount. Then Cloverleaf will have no problem.

So you have to remove the mount completely and create it again with the above mentioned parameters. Don’t forget to correct etc/fstab as well.

More info you will find here:  http://linux.die.net/man/8/mount.cifs

Kind regards,

Marc Pleijers

VANAD Enovation

The Netherlands

Marc Pleijers
Senior Integration Consultant
Enovation BV
The Netherlands

[Author]

Replies