All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Denis V. Nagorny" <dvnagorny@compcenter.org>
To: linux-nfs@vger.kernel.org
Subject: Re: Randomly inaccessible files through NFS
Date: Fri, 17 Aug 2012 14:26:00 +0400	[thread overview]
Message-ID: <502E1C38.2060104@compcenter.org> (raw)
In-Reply-To: <502B55A3.3030007@compcenter.org>

15.08.2012 11:54, Denis V. Nagorny пишет:
> Hello,
>
> Using Scientific Linux 6.1 (I think it's equal to RH EL 6.1) we met 
> the strange issue.  Several last months we have problem. After one or 
> two days of successful work, files on nfs server begins to be randomly 
> unacessible.
> I doesn't mean that files becames hidden or something like this. It 
> means that attempts to open some random files may be unsuccessful. 
> Usually restart of nfs server makes situation better but for several 
> days only. There are no any messages about errors in logs on server 
> and clients machines. Can anybody point me how can I try to understand 
> what happens at least. Sorry for my english.
>
> Denis.

Hello again,

I've made some additional experiments. It looks like nfs clients can be 
in one of two states: "quite stable" and "quite unstable". Clients are 
usually stable but after some heavy job with a lot of I/O with NFS 
server clients become "quite unstable" and fails even with single file 
operations with NFS server. In this state I can't unmount NFS shares and 
so on.  I've tried to analyse with wireshark and found that in unstable 
state there are a lot of NFS4ERR_EXPIRED answers from NFS server.  In 
one of experiments I've changed NICs in both machines involved - result 
the same. So I'm still looking for the ways to understand the problem.
Can anybody give me any advices?

Denis

  reply	other threads:[~2012-08-17 10:25 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-08-15  7:54 Randomly inaccessible files through NFS Denis V. Nagorny
2012-08-17 10:26 ` Denis V. Nagorny [this message]
2012-08-17 10:50   ` Adrien Kunysz
2012-08-17 12:28     ` Denis V. Nagorny

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=502E1C38.2060104@compcenter.org \
    --to=dvnagorny@compcenter.org \
    --cc=linux-nfs@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 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.