From: Knut Petersen <Knut_Petersen@t-online.de>
To: Trond Myklebust <trond.myklebust@fys.uio.no>
Cc: linux-kernel@vger.kernel.org, neilb@cse.unsw.edu.au,
nfs@lists.sourceforge.net
Subject: Re: [BUG] nfs version 2 broken
Date: Wed, 01 Feb 2006 07:34:39 +0100 [thread overview]
Message-ID: <43E0567F.20004@t-online.de> (raw)
In-Reply-To: <1138774519.7861.4.camel@lade.trondhjem.org>
Trond Myklebust schrieb:
>What kind of server is this that you are using? The above message
>basically means that it is handing out inodes with a link count of 0.
>
>Cheers,
> Trond
>
>
Server:
=====
AOpen i915GMm-HFS with Pentium M, linux kernel 2.6.15-git7
running a system that startet as SuSE 9.2. Nfs-utils are still
the original 1.0.6, grep -i nfs linuxbuild/.config gives
CONFIG_NFS_FS=y
CONFIG_NFS_V3=y
# CONFIG_NFS_V3_ACL is not set
# CONFIG_NFS_V4 is not set
# CONFIG_NFS_DIRECTIO is not set
CONFIG_NFSD=y
CONFIG_NFSD_V3=y
# CONFIG_NFSD_V3_ACL is not set
# CONFIG_NFSD_V4 is not set
CONFIG_NFSD_TCP=y
CONFIG_NFS_COMMON=y
Client
====
kernel build from the same source,
CONFIG_NFS_FS=y
CONFIG_NFS_V3=y
# CONFIG_NFS_V3_ACL is not set
# CONFIG_NFS_V4 is not set
# CONFIG_NFS_DIRECTIO is not set
CONFIG_NFSD=y
CONFIG_NFSD_V3=y
# CONFIG_NFSD_V3_ACL is not set
# CONFIG_NFSD_V4 is not set
CONFIG_NFSD_TCP=y
CONFIG_ROOT_NFS=y
CONFIG_NFS_COMMON=y
cu,
Knut
next prev parent reply other threads:[~2006-02-01 6:34 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-02-01 6:07 [BUG] nfs version 2 broken Knut Petersen
2006-02-01 6:15 ` Trond Myklebust
2006-02-01 6:34 ` Knut Petersen [this message]
2006-02-01 6:35 ` Trond Myklebust
2006-02-01 6:46 ` Knut Petersen
2006-02-01 6:46 ` Knut Petersen
2006-02-01 7:13 ` Knut Petersen
2006-02-01 7:13 ` Knut Petersen
2006-02-01 16:41 ` Trond Myklebust
2006-02-01 19:19 ` Knut 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=43E0567F.20004@t-online.de \
--to=knut_petersen@t-online.de \
--cc=linux-kernel@vger.kernel.org \
--cc=neilb@cse.unsw.edu.au \
--cc=nfs@lists.sourceforge.net \
--cc=trond.myklebust@fys.uio.no \
/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.