mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Trond Myklebust <trond.myklebust@fys.uio.no>
To: Adrian Cox <adrian@humboldt.co.uk>
Cc: linux-kernel@vger.kernel.org
Subject: Re: Problems with 2.6.4-rc2 NFS server and diskless clients
Date: Tue, 09 Mar 2004 10:52:02 -0500	[thread overview]
Message-ID: <1078847522.4067.10.camel@nidelv.trondhjem.org> (raw)
In-Reply-To: <1078846645.1441.14.camel@newt>

På ty , 09/03/2004 klokka 10:37, skreiv Adrian Cox:
> Using 2.6.4-rc2  on the NFS server together with Debian unstable
> (nfs-kernel-server version 1:1.0.6-1), diskless clients can no longer
> mount their root filesystems. The same configuration works with a 2.4
> kernel on the server.
> 
> The client reports "nfs_get_root: getattr error = 116". No error
> messages appear in the server logs. And the old recipe of exporting with
> "no_subtree_check" makes no difference.
> 
> Anybody have any suggestions?

There's already a patch for that in the Bitkeeper tree.

Cheers

  Trond

# This is a BitKeeper generated diff -Nru style patch.
#
# ChangeSet
#   2004/03/06 16:11:47-08:00 trond.myklebust@fys.uio.no 
#   [PATCH] Fix knfsd filehandles...
#   
#   Here's a fix for an obvious typo in changeset
#   neilb@cse.unsw.edu.au|ChangeSet|20040305155724|31191
#   that was causing ESTALE errors galore on my NFS testrig.
# 
# fs/nfsd/nfsfh.c
#   2004/03/06 13:46:05-08:00 trond.myklebust@fys.uio.no +1 -0
#   Fix knfsd filehandles...
# 
diff -Nru a/fs/nfsd/nfsfh.c b/fs/nfsd/nfsfh.c
--- a/fs/nfsd/nfsfh.c	Tue Mar  9 10:51:22 2004
+++ b/fs/nfsd/nfsfh.c	Tue Mar  9 10:51:22 2004
@@ -396,6 +396,7 @@
 				 */
 				mk_fsid_v0(datap, ex_dev,
 					exp->ex_dentry->d_inode->i_ino);
+				break;
 			case 1:
 				/* fsid_type 1 == 4 bytes filesystem id */
 				mk_fsid_v1(datap, exp->ex_fsid);


      reply	other threads:[~2004-03-09 15:52 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-03-09 15:37 Adrian Cox
2004-03-09 15:52 ` Trond Myklebust [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=1078847522.4067.10.camel@nidelv.trondhjem.org \
    --to=trond.myklebust@fys.uio.no \
    --cc=adrian@humboldt.co.uk \
    --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

all inboxes | Powered by JetHome®