Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Takes ~20-30 seconds to start for the first time if there are big NFS mounts #3515

Open
actionless opened this issue Jan 22, 2025 · 3 comments

Comments

@actionless
Copy link

actionless commented Jan 22, 2025

Distribution

Arch Linux

Package version

6.4.3

Frequency

Always

Bug description

Nemo takes ~20-30 seconds to start for the first time if there are big NFS mounts.

Steps to reproduce

  1. mount big nfs storage (in my case 1 tb)
  2. start nemo

Expected behavior

nemo would take to start same time as usually

Additional information

No response

@leigh123linux
Copy link
Contributor

The amount of info posted is pathetic!
Provide info on how the shares are mounted.

@actionless
Copy link
Author

here's the fstab record:

cloyster:/home/lie/ai_local   /home/lie/ai_local    nfs vers=4,exec,soft 0 0

it's rather default except for soft, but before adding soft the problem with the start time was still there

@actionless
Copy link
Author

actionless commented Jan 22, 2025

network share itself is pretty fast (it's a NVM storage over 1Gb ethernet) and except for this particular bug with nemo startup time nothing weird was noted with it

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants