Server Fault is a question and answer site for system and network administrators. Join them; it only takes a minute:

Sign up
Here's how it works:
  1. Anybody can ask a question
  2. Anybody can answer
  3. The best answers are voted up and rise to the top

I have a problem with a bunch of CIFS mounts that look like this:

// /home/windows-shared/remote-share cifs defaults,user=xxx,password=xxx,uid=603,gid=603       0 0

This issue occurs after a while, usually after a day when the users boot their machines in the morning and their shares don't work remotely any more.

So when I try to do a ls I get this:

ls: cannot access /home/windows-shared/remote-share: Host is down

I get nothing related in dmesg. The problem with this is that now any read call to this part of the system just hangs so as a solution I would rather have a faster error rather than hanging indefinitely.

After reading a bit the man page of mount.cifs it appears that by default every mount is soft meaning that it would timeout eventually. The problem is that it takes a way too long to timeout.


Adding these parameters to the mount command didn't help either:

share|improve this question
Have you tried using timeo=n and retrans=m to shorten the timeout interval? – MadHatter Mar 12 '14 at 9:41
@MadHatter Trying it now. I'll see if this works. Thanks. – Alexandru Plugaru Mar 12 '14 at 9:52
@MadHatter adding those params doesn't really change anything – Alexandru Plugaru Mar 13 '14 at 9:22
What do you mean by "doesn't change anything"; could you be a bit more quantitative, and maybe descriptive, too? – MadHatter Mar 13 '14 at 14:05
@MadHatter by doesn't change anything I mean that the changes you suggested didn't improve the situation. I specify, adding those parameters didn't improve or worsen the issue. Any file call still hangs the process. – Alexandru Plugaru Mar 13 '14 at 15:39

Your Answer


By posting your answer, you agree to the privacy policy and terms of service.

Browse other questions tagged or ask your own question.