All of lore.kernel.org
 help / color / mirror / Atom feed
From: Sven Geggus <lists@fuchsschwanzdomain.de>
To: linux-kernel@vger.kernel.org
Subject: Re: 2.6.29+ NFS-Server Problem "reconnect_path: npd != pd"
Date: Thu, 21 May 2009 17:48:51 +0000 (UTC)	[thread overview]
Message-ID: <gv4463$6fn$1@ultimate100.geggus.net> (raw)
In-Reply-To: 1242927133.6687.4.camel@heimdal.trondhjem.org

Trond Myklebust <trond.myklebust@fys.uio.no> wrote:

> So what is the underlying filesystem that you are exporting, and what
> does your /etc/exports file look like?

The underlying filesystem is xfs and /etc/exports (unchanged) is here:

--cut--
# /etc/exports: the access control list for filesystems which may be exported
#		to NFS clients.  See exports(5).
/               192.168.3.2(rw,no_root_squash,async,subtree_check)
/home/sven	192.168.3.2(rw,no_root_squash,async,subtree_check) 192.168.3.6(rw,no_root_squash,async,subtree_check) 192.168.3.8(rw,no_root_squash,async,subtree_check)
/home/mp3	192.168.3.2(rw,no_root_squash,async,subtree_check) 192.168.3.6(rw,no_root_squash,async,subtree_check) 192.168.3.8(rw,no_root_squash,async,subtree_check)
/home/sven/filme 192.168.3.7(ro,async,subtree_check)
/home/kathi910	192.168.3.7(rw,no_root_squash,async,no_subtree_check)
--cut--

192.168.3.2 is the client which causes the error, I didn't notice the
error on the other clients, but they are not used that often.

Especially 192.168.3.7 does seem to work.

Regards

Sven

-- 
"We don't know the OS that God uses, but the Vatican uses Linux"
                               (Sister Judith Zoebelein, Vatican Webmaster)

/me is giggls@ircnet, http://sven.gegg.us/ on the Web

  reply	other threads:[~2009-05-21 17:48 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-05-21 14:20 2.6.29+ NFS-Server Problem "reconnect_path: npd != pd" Sven Geggus
2009-05-21 16:49 ` Trond Myklebust
2009-05-21 16:57   ` Sven Geggus
     [not found]     ` <20090521165751.GA4428-6gBBswh35yKsTnJN9+BGXg@public.gmane.org>
2009-05-21 17:32       ` Trond Myklebust
2009-05-21 17:32         ` Trond Myklebust
2009-05-21 17:48         ` Sven Geggus [this message]
2009-05-21 18:12           ` Trond Myklebust
     [not found]             ` <1242929546.22947.11.camel-rJ7iovZKK19ZJLDQqaL3InhyD016LWXt@public.gmane.org>
2009-05-28 20:28               ` J. Bruce Fields
2009-05-28 20:28                 ` J. Bruce Fields
2009-05-28 20:32                 ` Sven Geggus
2009-06-19 12:14                   ` Mathias Kretschmer
     [not found]                     ` <200906191414.02674.mathias-ZcF2+9dVbKo@public.gmane.org>
2009-06-19 12:46                       ` Sven Geggus
2009-06-19 12:46                         ` Sven Geggus
     [not found]                         ` <20090619124611.GA16337-6gBBswh35yKsTnJN9+BGXg@public.gmane.org>
2009-06-27 19:39                           ` Leandro Lucarella
2009-06-27 19:39                             ` Leandro Lucarella
2009-06-22 19:55           ` Thomas Petersen

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='gv4463$6fn$1@ultimate100.geggus.net' \
    --to=lists@fuchsschwanzdomain.de \
    --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 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.