All of lore.kernel.org
 help / color / mirror / Atom feed
From: William Dauchy <william@gandi.net>
To: William Dauchy <william@gandi.net>
Cc: Linux NFS mailing list <linux-nfs@vger.kernel.org>,
	Trond Myklebust <trond.myklebust@primarydata.com>
Subject: Re: strange behavior with nfsv3 using linux v4.1
Date: Sat, 7 Nov 2015 09:41:50 +0100	[thread overview]
Message-ID: <20151107084150.GI12546@gandi.net> (raw)
In-Reply-To: <20151106225715.GH12546@gandi.net>

[-- Attachment #1: Type: text/plain, Size: 400 bytes --]

On Nov06 23:57, William Dauchy wrote:
> I am seeing strange behaviors with a single nfsv3 mount on linux
> v4.1.x. I first started to see two kworker in D state while I was not
> doing anything. The server is an opensolaris nfs server.

forgot to mention this nfsv3 mount is a using CONFIG_ROOT_NFS
it's a read only mount point

the client seems to be looping on revalidation.
-- 
William

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 181 bytes --]

  reply	other threads:[~2015-11-07  8:41 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-11-06 22:57 strange behavior with nfsv3 using linux v4.1 William Dauchy
2015-11-07  8:41 ` William Dauchy [this message]
2015-11-11 21:28   ` William Dauchy

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=20151107084150.GI12546@gandi.net \
    --to=william@gandi.net \
    --cc=linux-nfs@vger.kernel.org \
    --cc=trond.myklebust@primarydata.com \
    /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.