All of lore.kernel.org
 help / color / mirror / Atom feed
From: Benny Halevy <bhalevy@tonian.com>
To: Steve Dickson <SteveD@redhat.com>
Cc: Linux NFS Mailing list <linux-nfs@vger.kernel.org>
Subject: Re: pNFS: Single Node pNFS Server
Date: Sun, 05 Feb 2012 12:09:46 +0200	[thread overview]
Message-ID: <4F2E556A.7040707@tonian.com> (raw)
In-Reply-To: <4F2D6B97.6050102@RedHat.com>

Thanks Steve!

The required config options are:
CONFIG_NFSD_V4=y
CONFIG_PNFSD=y
CONFIG_PNFSD_LOCAL_EXPORT=y

The following config options are optional and may break your client:
CONFIG_PNFSD_LEXP_LAYOUT_SEGMENTS=y
CONFIG_PNFSD_LEXP_LAYOUT_SEGMENT_SIZE=65536

Benny

On 2012-02-04 19:32, Steve Dickson wrote:
> Hello all,
> 
> To help with the testing of pNFS clients, I making 
> available a single node pNFS server (the  pnfsd-lexp 
> branch of Benny's git tree) in Fedora based kernel 
> and nfs-utils RPMs. This server only supports file layouts. 
> 
> Your need to be running a Fedora 16 to use these RPMs.
> The RPMs are in a yum repository. Download this repo:
> 
>    http://steved.fedorapeople.org/pnfs.repo
> and then do a yum update on a F16 machine.
> 
> Or you can access the RPMs directly at 
>     http://steved.fedorapeople.org/repos/pnfs/devel/
> 
> The patches used to create the RPMs ar at:
>     http://steved.fedorapeople.org/repos/pnfs/devel/pnfsd-3.3.0-0.rc2.git1.1.patch
>     http://steved.fedorapeople.org/repos/pnfs/devel/pnfs-export-1.2.5-11.patch
> 
> Happy hunting! 
> 
> steved.
> 
> 
> 
> --
> To unsubscribe from this list: send the line "unsubscribe linux-nfs" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at  http://vger.kernel.org/majordomo-info.html

      reply	other threads:[~2012-02-05 10:09 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-02-04 17:32 pNFS: Single Node pNFS Server Steve Dickson
2012-02-05 10:09 ` Benny Halevy [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=4F2E556A.7040707@tonian.com \
    --to=bhalevy@tonian.com \
    --cc=SteveD@redhat.com \
    --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.