Description of problem: After successful file transfers, I move a file from a client to an NFS server and the NFS mount crash and the client graphical interface (KDE desktop) freezes. My configuration : NFS client (mga-3 ) : 192.168.0.1 $ cat /etc/fstab|grep 192.168.0.2 192.168.0.2:/home /mnt/asus/home nfs nolock,noauto,users,rw 0 0 $ mount|grep 192.168.0.2 192.168.0.2:/home on /mnt/asus/home type nfs4 (rw,nosuid,nodev,noexec,relatime,vers=4.0,rsize=131072,wsize=131072,namlen=255,hard,proto=tcp,port=0,timeo=600,retrans=2,sec=sys,clientaddr=192.168.0.1,local_lock=none,addr=192.168.0.2) NFS server (mga-3) : 192.168.0.2 After unmounting from another tty (umount -l /mnt/asus/home), my desktop unfreezes. But on the server side, the network is out. After restarting the server network (systemctl restart network.service), I can again mount my remote NFS directory. Version-Release number of selected component (if applicable): How reproducible: always after a few file transfer Steps to Reproduce: 1. mount the NFS directory 2. copy some files from the client to the server 3. Reproducible: Steps to Reproduce:
Keywords: (none) => TriagedAssignee: bugsquad => guillomovitch
Can you reproduce the issue by any kind of write access on the server, such as for instance creating an empty file through touch command ?
Status: NEW => ASSIGNED
It created up to 10000 empty files on the server from the client and had no problem. But sometimes, just transfering one file of 700 MB makes the client very slow or freeze. Only restarting the server network (systemctl restart network.service) restores the connection and normal behaviour on the client side (unfreezing the desktop).
Mageia 3 changed to end-of-life (EOL) status 4 months ago. http://blog.mageia.org/en/2014/11/26/lets-say-goodbye-to-mageia-3/ Mageia 3 is no longer maintained, which means that it will not receive any further security or bug fix updates. As a result we are closing this bug. If you can reproduce this bug against a currently maintained version of Mageia please feel free to click on "Version" change it against that version of Mageia and reopen this bug. Thank you for reporting this bug and we are sorry it could not be fixed. -- The Mageia Bugsquad
Status: ASSIGNED => RESOLVEDResolution: (none) => OLD