Hide Forgot
Description of problem: Attempting to copy a folder of files to a remote file system via NFS or CIFS fails every time after creating the remote folder and one file. No problem copying when using F14 and CIFS (never used NFS with F14). Tried Live CD with exact same problem. Version-Release number of selected component (if applicable): Every kernel released for F15 so far. How reproducible: Always Steps to Reproduce: 1.Mount remote file system using either CIFS or NFS 2.Copy folder to remote system (drag'n'drop or via commandline) 3. Actual results: Nautilus hangs, commandline is unresponsive. Expected results: Successful copy operation without pause or hang Additional info: The only thing noted in /var/log/messages, every 4 minutes (this is an NFS example): Jul 10 16:15:59 toshiba kernel: [ 1305.056051] nfs: server dlink not responding, timed out
what's the server running ? Can you still ping it when nfs/cifs stops responding ? (trying to determine if this is maybe a NIC problem, as affecting both protocols seems weird)
Server is typically my D-Link NAS (DNS-320) which supports CIFS, NFS, ftp, AFP, UPnP. From a Windows machine, CIFS and UPnP work fine. The NAS OS is supposedly Linux and I have the latest firmware installed. All I'm attempting to do is to copy photos from my F15 laptop to the NAS for backup and UPnP streaming. The NAS is still there with pings and accessible from other machines. As for NIC possibilities, I use a Belkin Cardbus N adapter using RPMfusion's rt2860 driver. From the Live CD, I removed the card and used the built-in Intel ipw2200 device with the default driver. Doesn't appear to be a NIC problem.
Forgot to say that this happens connecting to a Windows 7 machine, too.
GIO switched to using splice(2) for file copy, could this be the source of problems?
Is there something I can try from, say, F14 to test this? Any copy to or from a network resource fails for me. The Nautilus display indicates a couple of MB copied and then it just stalls forever.
Just tried a bunch of small files to see if size was important. Used /etc/yum.repos.d as the test. 26 files, failed after 4.3MB was transferred, stalled on the 9th file. I have to reboot to regain control. The shutdown takes 5 minutes - a network mount timeout?
is this still a problem with the 2.6.43.1 update ?
Long since moved on to F15. No problem there.