public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Bill Davidsen <davidsen@tmr.com>
To: linux-kernel@vger.kernel.org
Subject: Re: iSCSI target stops sending responses to login requests
Date: Mon, 11 Aug 2014 14:30:39 -0400	[thread overview]
Message-ID: <53E90BCF.3030004@tmr.com> (raw)
In-Reply-To: <CAHjPQwNFr5gA-vcQa0nk98U0yPgEdCj+iXWeP0_mXpjXdrW+sA@mail.gmail.com>

Evgenii Lepikhin wrote:
> Hello,
>
> We have several NAS servers with kernels 3.4.xx-3.13.xx. We've got a
> problem: after 1..4 months of work target servers stops responding to
> login requests.
>
I have seen a very similar problem on file servers, in my case an NFS workgroup 
server. I thought it was due to down level 3.8.13-fc17 kernel, not scheduled for 
upgrade for a few months yet, probably over Labor Day weekend.

However, existing connections on the machine also will respond to ENTER with a 
newline, but any connand requiring a new process hangs. It behaves as if the 
machine was out of processes, but I traced processes every few minutes and saw 
no buildup.

In addition, the machine hosts a virtual machine which continues to work just 
fine. Does any of this match additional issues you didn't mention or haven't 
checked?

[__ snip __]
>
> Any ideas?
>
May or may not be related, we have a console open on the machine and can verify 
the odd behavior.

-- 
Bill Davidsen <davidsen@tmr.com>
   "We have more to fear from the bungling of the incompetent than from
the machinations of the wicked."  - from Slashdot

      reply	other threads:[~2014-08-11 18:53 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-08-10  7:40 iSCSI target stops sending responses to login requests Evgenii Lepikhin
2014-08-11 18:30 ` Bill Davidsen [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=53E90BCF.3030004@tmr.com \
    --to=davidsen@tmr.com \
    --cc=linux-kernel@vger.kernel.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