All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Łukasz Maśko" <masko-/XNhcdyn+gCn9IrpMBEE/Q@public.gmane.org>
To: linux-cifs-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
Subject: Re: How to deal with such hanging processes?
Date: Sat, 28 Jan 2012 15:50:10 +0100	[thread overview]
Message-ID: <201201281550.10554@laptok.ed.pl> (raw)
In-Reply-To: <20120128140830.2b48a0c8.ralda-Mmb7MZpHnFY@public.gmane.org>

Dnia sobota, 28 stycznia 2012, ralda-Mmb7MZpHnFY@public.gmane.org napisał:
[...]
> That cifs_max_pending=2 module parameter helps a lot on my side. It not
> only avoids many cases the cifs process gets stuck it even leads to
> the interesting behavior that such processes vanish (accept the kill)
> after a couple of minutes. In those cases the device even return to a
> working state without an reboot. After that you may unmount normal or
> continue to access the NAS device. Awesome those stuck periods but
> better than having to reboot. Especially as those collisions happen
> much less than without the module parameter.

Exactly. Same for me.
-- 
Łukasz Maśko                                           GG:   2441498    _o)
Lukasz.Masko(at)ipipan.waw.pl                                           /\\
Registered Linux User #61028                                           _\_V
Ubuntu: staroafrykańskie słowo oznaczające "Nie umiem zainstalować Debiana"

  parent reply	other threads:[~2012-01-28 14:50 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-01-27 20:33 How to deal with such hanging processes? Łukasz Maśko
     [not found] ` <201201272133.35986-D2Dg4Jie/XezyIjkdXusMg@public.gmane.org>
2012-01-28 12:30   ` Jeff Layton
     [not found]     ` <20120128073021.4eca547e-9yPaYZwiELC+kQycOl6kW4xkIHaj4LzF@public.gmane.org>
2012-01-28 13:08       ` ralda-Mmb7MZpHnFY
     [not found]         ` <20120128140830.2b48a0c8.ralda-Mmb7MZpHnFY@public.gmane.org>
2012-01-28 14:50           ` Łukasz Maśko [this message]
2012-01-28 14:54       ` Łukasz Maśko

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=201201281550.10554@laptok.ed.pl \
    --to=masko-/xnhcdyn+gcn9irpmbee/q@public.gmane.org \
    --cc=linux-cifs-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.