Linux CIFS filesystem development
 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:54:25 +0100	[thread overview]
Message-ID: <201201281554.25466@laptok.ed.pl> (raw)
In-Reply-To: <20120128073021.4eca547e-9yPaYZwiELC+kQycOl6kW4xkIHaj4LzF@public.gmane.org>

Dnia sobota, 28 stycznia 2012, Jeff Layton napisał:
[...]
> The way to deal with them is to solve the problem that causes them to
> hang in the first place. Once they're stuck like that, there's really
> little you can do until the page lock is released. The messages from
> the ring buffer suggest that the server is sending corrupt replies to
> the requests. A network capture might help confirm that.

It is a bit hard to capture it since it is nondeterministic :-/ I'll try 
anyway.

> Is this the same NAS that requests a maxmpx of 1? If so, the fact that
> cifs sends more than one request a time to this server might be the
> ultimate cause.

It was in another thread for a different NAS, but it seems, that it is the 
same in my case.
 
> Obviously the server should handle that situation without corrupting
> its replies, but cifs is clearly broken in this regard and shouldn't be
> sending more than one request at a time to such a server. I doubt
> there's anything you can do until Steve fixes that bug.

So I'm waiting patiently, that's all I can do :-)

-- 
Łukasz Maśko                                                            _o)
Lukasz.Masko(at)ipipan.waw.pl                                           /\\
Registered Linux User #61028                                           _\_V

      parent reply	other threads:[~2012-01-28 14:54 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
2012-01-28 14:54       ` Łukasz Maśko [this message]

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=201201281554.25466@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox