From: Jim Rees <rees@umich.edu>
To: DENIEL Philippe <philippe.deniel@cea.fr>
Cc: Benny Halevy <bhalevy@panasas.com>,
peter honeyman <honey@citi.umich.edu>,
linux-nfs@vger.kernel.org
Subject: Re: Deploying a pNFS / LAYOUT4_BLOCK_VOLUME configuration
Date: Wed, 15 Sep 2010 10:42:45 -0400 [thread overview]
Message-ID: <20100915144245.GB30965@merit.edu> (raw)
In-Reply-To: <4C90D78F.5000307@cea.fr>
DENIEL Philippe wrote:
Apparently writing to /proc/fs/pnfs_block/ctl does not work. Do you
have an idea on what I should do to fix this ?
I have not worked with the server side but will be in the coming months.
Maybe someone on the list can help.
>I have added a section on the block layout client to the Fedora client setup
>wiki page:
>
>http://wiki.linux-nfs.org/wiki/index.php/Fedora_pNFS_Client_Setup
Is there a layoutdriver to modprobe on the client or is it embedded
in the kernel itself ?
You could build it in but I normally build it as a module. The startup
script assumes it's a module and probes it:
fedora# grep blocklayoutdriver /etc/init.d/blkmapd
modprobe -q blocklayoutdriver
fedora#
Right now the nfs-utils rpm doesn't install the startup script. I'll fix
this but for now just copy it from the source:
cp nfs-utils/utils/blkmapd/etc/initd/initd.redhat /etc/init.d/blkmapd
chmod +x /etc/init.d/blkmapd
prev parent reply other threads:[~2010-09-15 14:42 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-09-14 12:40 Deploying a pNFS / LAYOUT4_BLOCK_VOLUME configuration DENIEL Philippe
2010-09-14 14:04 ` Benny Halevy
2010-09-14 14:17 ` Jim Rees
2010-09-15 14:04 ` Jim Rees
2010-09-15 14:26 ` DENIEL Philippe
2010-09-15 14:42 ` Jim Rees [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=20100915144245.GB30965@merit.edu \
--to=rees@umich.edu \
--cc=bhalevy@panasas.com \
--cc=honey@citi.umich.edu \
--cc=linux-nfs@vger.kernel.org \
--cc=philippe.deniel@cea.fr \
/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;
as well as URLs for NNTP newsgroup(s).