Do Plasma or Dolphin have known issues with NFS mounts or is this Fedora's fault?

Help
, ,
1

Again, I can’t tell if the problem is with Fedora or with Plasma.

Plasma locked up hard yesterday, twice, no mouse, no keyboard input, I had to press the reset button. That’s twice too many for a single day.

Both times I was accessing something in /NAS which is an NFS mount.

The first time I selected a folder and pressed the Delete key and the entire desktop locked up instantly.

The second time I dragged a folder from /NAS to my desktop, released and selected “Copy” and again, instant lockup.

Later , I was able to manipulate files and folders in /NAS and nothing happened.

Is this another “Wayland issue”?

2

Hi - it might be worthwhile checking your system journal at the time those freezes occurred, to see if anything got logged before everything completely froze?

If you know roughly what times it happened, you could use sudo journalctl --since="yyyy-mm-dd hh:mm:ss" --until="yyyy-mm-dd hh:mm:ss" to try to narrow down to that time and see what was recorded.

Did you get any messages that indicated an issue with the display server? Just checking as you mentioned that you were thinking it might be related to Wayland, and I wasn’t intuitively sure what the connection was there.

Just a thought - it sounds like both times there was an issue involved a folder located on the desktop? Do you get any different result if you try interacting with that folder using a Dolphin window that’s navigated to the Desktop folder?

And for system freeze recovery in general, one thing that might be worth a shot is enabling the “Magic SysRq” key: QA/Sysrq - Fedora Project Wiki It hasn’t always worked, but Alt+PrtSc,R,E,I,S,U,B has at least more gracefully bailed out of a couple of freeze-up situations over the past couple years :slight_smile:

3

This was a link, actually a .desktop file, on the desktop pointing to /NAS which was the NFS mount.

Unfortunately, I wiped and reinstalled today, to give Fedora 42 rawhide a try, so no more logs. It happened twice in a row, then I was using that link without any more problems.

For now, I’ve gone back to using SFTP, though it’s somewhat slow at times compared to NFS or even SMB. Anyway, I digress…

I’ll look into that “Magic SysRq”.

Thank you :grinning:

4

Was the NFS fs mounted ? Or did you expect to get an automount behavior ?

5

I did:
sudo mount -t nfs 192.168.1.100:/nas /NAS

Then added this to the fstab:
192.168.1.100:/nas /NAS nfs nofail 0 0

And it normally worked, automounted on every boot and other than these two crashes I had no difficulties accessing files on it.

6

@anonnetuser:

Personally, I prefer to use the systemd autofs service for NFS mounts to NAS devices.

 > time ls /mnt/NAS-YYY-001/NFS/xxx/
???001  ???005  Repo_Packages_Xtra_Leap-15.5  smb.conf

real    0m0,126s
user    0m0,000s
sys     0m0,005s
 >

The only Catch-22, at least for the case of my QNAP NAS is, that the mount point “NFS” is extremely unresponsive – I always have to hit the user directory below that mount point to achieve a mount time of around about 125 milliseconds …

And, Dolphin also has to use the “user directory below the NFS mount point” trick to make it behave properly … :smiling_imp:

BTW, I’m using an openSUSE Leap 15.6 system.

7

I’ve just gone back to SFTP for now. Copy speed seems a bit slower but it’s always responsive.