ProgrammingThis forum is for all programming questions.
The question does not have to be directly related to Linux and any language is fair game.
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
Example2:
pDir = opendir("/mnt/win/data");
if (NULL != pDir)
{
if ((dp = readdir(pDir)) != NULL)
{
iRet = stat(dp->d_name, &StatBuff);
if (-1 == iRet)
{
perror("statfail");
}
}
}
I have mounted a windows share folder on /mnt. When i gave any directory within /mnt/ to stat function it fails with errorno 75. perror shows "Value too large for defined data type".
Example 1 is fail but Example 2 works fine.
Can any one tell me meanning of error or why Example 1 gets fail here?
As it happens I am in the midst of a samba / cifs related project:
Mounting with noserverino forces the samba client to generate inode numbers, where without the option the inode numbers would be created by the server.
Looks like the server is generating huge (64 bit) inode numbers, but one or more apps on your system have been compiled without support for that by the distro maintainers.
I have not tried any of the below options as I work exclusively with 64 bit machines and I suspect your client is 32 bit, but:
It may be that you simply need to add -D_FILE_OFFSET_BITS=64 when compiling _your_ app, OR
If the compile problem is with your samba client software, you could try compiling samba-client from source with -D_FILE_OFFSET_BITS=64 as a configure option, OR
Alternatively it looks like this could be fixed by the distro maintainers, so you could just wait.
Looks like the nolinux mentioned was a blind alley, so I would remove that.
As it happens I am in the midst of a samba / cifs related project:
Mounting with noserverino forces the samba client to generate inode numbers, where without the option the inode numbers would be created by the server.
Looks like the server is generating huge (64 bit) inode numbers, but one or more apps on your system have been compiled without support for that by the distro maintainers.
I have not tried any of the below options as I work exclusively with 64 bit machines and I suspect your client is 32 bit, but:
It may be that you simply need to add -D_FILE_OFFSET_BITS=64 when compiling _your_ app, OR
If the compile problem is with your samba client software, you could try compiling samba-client from source with -D_FILE_OFFSET_BITS=64 as a configure option, OR
Alternatively it looks like this could be fixed by the distro maintainers, so you could just wait.
Looks like the nolinux mentioned was a blind alley, so I would remove that.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.