RedHat and SuSE have unreliable cp over cifs network, resource temporarily unavailabl
Linux - NetworkingThis forum is for any issue related to networks or networking.
Routing, network cards, OSI, etc. Anything 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.
RedHat and SuSE have unreliable cp over cifs network, resource temporarily unavailabl
Current setup:
Windows 2003 server machine has a CIFS/SMB share sharing something like C:\ = //windowshost/C is being shared.
Other Linux machines are mounting this share like so:
//windowshost/C on /mnt/windowshost/C type cifs (rw,mand)
Most of the time i am able to browse, copy, edit files through the mount but occasionally I will get the following error when copying files to the mount:
cp: accessing `/mnt/windowshost/C/some/path/here/': Resource temporarily unavailable
The thing is, an automated python script is copying files and sometimes getting this resource error, when i manually browse the mount its fine. The mount is also not heavily used, each Linux host is probably copying a 100KB file once every 3-4 minutes, and there are about 3 hosts.
The windows machine has not been down and no network outtages. Any known issues to "Resource temporarily unavailable" errors? The Windows box is 2003 so its probably using SMB 1.0
According to the fcntl man page, you get EAGAIN when you attempt a nonblocking operation on a filesystem mounted with mandatory locking. Why are you setting the mand option? The default is advisory. Your other browsing is likely to open the files without setting O_NONBLOCK, so is not causing a problem.
According to the fcntl man page, you get EAGAIN when you attempt a nonblocking operation on a filesystem mounted with mandatory locking. Why are you setting the mand option? The default is advisory. Your other browsing is likely to open the files without setting O_NONBLOCK, so is not causing a problem.
When I mount with -t cifs, it gives me RW, MAND by default. I tried giving it the option nomand, but it looks like it ignores it and still defaults to MAND.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.