Helen, please note that the [email protected] mailing list was deprecated.
Forwarding to [email protected].
>From a quick glance I'm not sure what went wrong with your build,
Steve should know better :-)
Benny
On May. 19, 2010, 20:32 +0300, "Chen, Helen Y" <[email protected]> wrote:
Has anyone successfully build pnfs enabled nfs utils under Fedora 13?
I am running the kernel from:
http://steved.fedorapeople.org/repos/pnfs/13/x86_64/
I installed libtirpc{,-devel}, tcp_wrappers{,-devel}, libevent{,-devel},
nfs-utils-lib{,-devel},
libgssglue{,-devel}, libblkid{,-devel}, and libcap{,-devel}
per instructions from:
_http://wiki.linux-nfs.org/wiki/index.php/Configuring_pNFS/spnfsd#Kernel_and_nfs-utils_compilati__on_
<http://wiki.linux-nfs.org/wiki/index.php/Configuring_pNFS/spnfsd#Kernel_and_nfs-utils_compilation>
I used libnfsidmap{,-devel} bundled in:
Nfs-utils-lib-devel-1.1.5-1.fc13.X86_64.rpm
Finally, I downloaded _nfs-utils-1.2.2-4.1.pnfs.src.rpm_
<http://steved.fedorapeople.org/repos/pnfs/13/source/nfs-utils-1.2.2-4.1.pnfs.src.rpm>
from _http://steved.fedorapeople.org/repos/pnfs/13/source/_
I am having trouble building these utils. I failed to generate
?configure? when I ran autogen.sh:
/c//leaning up ............. done
//lobotomize//: putting auxiliary files in `.'.
libtoolize: copying file `./ltmain.sh'
libtoolize: putting macros in AC_CONFIG_MACRO_DIR, `aclocal'.
libtoolize: copying file `aclocal/libtool.m4'
libtoolize: copying file `aclocal/ltoptions.m4'
libtoolize: copying file `aclocal/ltsugar.m4'
libtoolize: copying file `aclocal/ltversion.m4'
libtoolize: copying file `aclocal/lt~obsolete.m4'
configure.ac:5: installing `./config.guess'
configure.ac:5: installing `./config.sub'
configure.ac:421: required file `tools/mountstats/Makefile.in' not found
configure.ac:421: required file `tools/nfs-iostat/Makefile.in' not found/
I deleted the two Makefile.in requirements from line 421 in configure.ac
because there were only python scripts inside those directories.
When I ran the ?configure? generated after the modification, it failed
with the following output:
/checking build system type... x86_64-unknown-linux-gnu
checking host system type... x86_64-unknown-linux-gnu
checking for a BSD-compatible install... /usr/bin/install -c
checking whether build environment is sane... yes
checking for gawk... gawk
checking whether make sets $(MAKE)... yes
checking whether to enable maintainer-specific portions of Makefiles... no
checking for style of include used by make... GNU
checking for gcc... gcc
checking whether the C compiler works... yes
checking for C compiler default output file name... a.out
checking for suffix of executables...
checking whether we are cross compiling... no
checking for suffix of object files... o
checking whether we are using the GNU C compiler... yes
checking whether gcc accepts -g... yes
checking for gcc option to accept ISO C89... none needed
checking dependency style of gcc... gcc3
checking how to run the C preprocessor... gcc -E
checking for grep that handles long lines and -e... /bin/grep
checking for egrep... /bin/grep -E
checking for ANSI C header files... no
checking for sys/types.h... yes
checking for sys/stat.h... yes
checking for stdlib.h... no
checking for string.h... yes
checking for memory.h... yes
checking for strings.h... yes
checking for inttypes.h... yes
checking for stdint.h... yes
checking for unistd.h... yes
checking for clnt_tli_create in -ltirpc... yes
checking /usr/include/tirpc/netconfig.h usability... yes
checking /usr/include/tirpc/netconfig.h presence... yes
checking for /usr/include/tirpc/netconfig.h... yes
checking for prctl... yes
checking for cap_get_proc in -lcap... yes
checking sys/capability.h usability... yes
checking sys/capability.h presence... yes
checking for sys/capability.h... yes
checking for libwrap... /
But libwrap is obviously installed based on the locate command:
#locate libwrap
/usr/lib/libwrap.so
/usr/lib/libwrap.so.0
/usr/lib/libwrap.so.0.7.6
/usr/lib64/libwrap.so
/usr/lib64/libwrap.so.0
/usr/lib64/libwrap.so.0.7.6
I am new at this and would appreciate any help you can provide.
Thanks,
Helen
On 05/26/2010 03:35 PM, Benny Halevy wrote:
> Helen, please note that the [email protected] mailing list was deprecated.
> Forwarding to [email protected].
>
>>From a quick glance I'm not sure what went wrong with your build,
> Steve should know better :-)
>
> Benny
>
> On May. 19, 2010, 20:32 +0300, "Chen, Helen Y" <[email protected]> wrote:
>
>
>
>
> Has anyone successfully build pnfs enabled nfs utils under Fedora 13?
> I am running the kernel from:
> http://steved.fedorapeople.org/repos/pnfs/13/x86_64/
>
> I installed libtirpc{,-devel}, tcp_wrappers{,-devel}, libevent{,-devel},
> nfs-utils-lib{,-devel},
> libgssglue{,-devel}, libblkid{,-devel}, and libcap{,-devel}
>
> per instructions from:
> _http://wiki.linux-nfs.org/wiki/index.php/Configuring_pNFS/spnfsd#Kernel_and_nfs-utils_compilati__on_
> <http://wiki.linux-nfs.org/wiki/index.php/Configuring_pNFS/spnfsd#Kernel_and_nfs-utils_compilation>
>
> I used libnfsidmap{,-devel} bundled in:
> Nfs-utils-lib-devel-1.1.5-1.fc13.X86_64.rpm
>
> Finally, I downloaded _nfs-utils-1.2.2-4.1.pnfs.src.rpm_
> <http://steved.fedorapeople.org/repos/pnfs/13/source/nfs-utils-1.2.2-4.1.pnfs.src.rpm>
> from _http://steved.fedorapeople.org/repos/pnfs/13/source/_
>
> I am having trouble building these utils. I failed to generate
> ‘configure’ when I ran autogen.sh:
>
> /c//leaning up ............. done
> //lobotomize//: putting auxiliary files in `.'.
> libtoolize: copying file `./ltmain.sh'
> libtoolize: putting macros in AC_CONFIG_MACRO_DIR, `aclocal'.
> libtoolize: copying file `aclocal/libtool.m4'
> libtoolize: copying file `aclocal/ltoptions.m4'
> libtoolize: copying file `aclocal/ltsugar.m4'
> libtoolize: copying file `aclocal/ltversion.m4'
> libtoolize: copying file `aclocal/lt~obsolete.m4'
> configure.ac:5: installing `./config.guess'
> configure.ac:5: installing `./config.sub'
> configure.ac:421: required file `tools/mountstats/Makefile.in' not found
> configure.ac:421: required file `tools/nfs-iostat/Makefile.in' not found/
>
> I deleted the two Makefile.in requirements from line 421 in configure.ac
> because there were only python scripts inside those directories.
>
> When I ran the ‘configure’ generated after the modification, it failed
> with the following output:
>
> /checking build system type... x86_64-unknown-linux-gnu
> checking host system type... x86_64-unknown-linux-gnu
> checking for a BSD-compatible install... /usr/bin/install -c
> checking whether build environment is sane... yes
> checking for gawk... gawk
> checking whether make sets $(MAKE)... yes
> checking whether to enable maintainer-specific portions of Makefiles... no
> checking for style of include used by make... GNU
> checking for gcc... gcc
> checking whether the C compiler works... yes
> checking for C compiler default output file name... a.out
> checking for suffix of executables...
> checking whether we are cross compiling... no
> checking for suffix of object files... o
> checking whether we are using the GNU C compiler... yes
> checking whether gcc accepts -g... yes
> checking for gcc option to accept ISO C89... none needed
> checking dependency style of gcc... gcc3
> checking how to run the C preprocessor... gcc -E
> checking for grep that handles long lines and -e... /bin/grep
> checking for egrep... /bin/grep -E
> checking for ANSI C header files... no
> checking for sys/types.h... yes
> checking for sys/stat.h... yes
> checking for stdlib.h... no
> checking for string.h... yes
> checking for memory.h... yes
> checking for strings.h... yes
> checking for inttypes.h... yes
> checking for stdint.h... yes
> checking for unistd.h... yes
> checking for clnt_tli_create in -ltirpc... yes
> checking /usr/include/tirpc/netconfig.h usability... yes
> checking /usr/include/tirpc/netconfig.h presence... yes
> checking for /usr/include/tirpc/netconfig.h... yes
> checking for prctl... yes
> checking for cap_get_proc in -lcap... yes
> checking sys/capability.h usability... yes
> checking sys/capability.h presence... yes
> checking for sys/capability.h... yes
> checking for libwrap... /
>
> But libwrap is obviously installed based on the locate command:
> #locate libwrap
> /usr/lib/libwrap.so
> /usr/lib/libwrap.so.0
> /usr/lib/libwrap.so.0.7.6
> /usr/lib64/libwrap.so
> /usr/lib64/libwrap.so.0
> /usr/lib64/libwrap.so.0.7.6
>
Yes I think I had that to, on FC12 did you also install tcp_wrappers-devel
[What configure does is look for the tcpd.h file.
So basically you:
- Look in configure what failed, and analyse what was missing here it was
"#include <tcpd.h>".
- yum provides "*/tcpd.h" - will show the tcp_wrappers-devel
Imagine that stupid me, I attempted to configure without reading the wiki first
and had about 10 of these, by the time I gut to libwrap it was becoming routine
RANT: I wish configure would leave the failing code on disk and specify the commands
I need to do to run the failing test. Or at least save and print the gcc output
of the failing test, rrrr ...
]
> I am new at this and would appreciate any help you can provide.
>
So there you have it
> Thanks,
> Helen
>
Boaz
On 05/26/2010 08:35 AM, Benny Halevy wrote:
> Has anyone successfully build pnfs enabled nfs utils under Fedora 13?
Yes... I run both the kernel and nfs-utils on a number of my test machines
to ensure they stability.
> I am running the kernel from:
> http://steved.fedorapeople.org/repos/pnfs/13/x86_64/
You might want to think about installing the yum repo at
http://steved.fedorapeople.org/pnfs.repo
so you can automatically get updates
>
> I am having trouble building these utils. I failed to generate
> ?configure? when I ran autogen.sh:
Here is the list of packages that need to be installed to
build the Fedora nfs-utils:
libgssglue-devel
libevent-devel
libcap-devel
nfs-utils-lib-devel
libtirpc-devel
libblkid-devel
openldap-devel
krb5-devel
tcp_wrappers-devel
To install these all at once, cat them into a file and then:
yum install `cat /tmp/list`
Next run the following commands:
./autogen.sh && ./configure && make
> I am new at this and would appreciate any help you can provide.
Well welcome... and please let know if there any more problems...
steved.
Hi Benny,
I installed Steve's fedora 13 pnfs kernel and your pnfs utils from the git tree on my 3 node testbed, a client, a MDS and a DS. I have successfully configured and mounted pNFS from the client, but can only create empty files in the directory. All attempts to write resulted in remote I/O errors. I discovered later that spnfsd is not running on the MDS. It dies silently every time I tried to start it. Running spnfsd with gdb indicated that it is reading /etc/spnfsd.conf correctly but crashed while writing to /proc/fs/spnfs/config. Your help will be appreciated?
Thanks in advance,
Helen
-----Original Message-----
From: Steve Dickson [mailto:[email protected]]
Sent: Wednesday, May 26, 2010 11:18 AM
To: Benny Halevy
Cc: NFS list; Chen, Helen Y
Subject: Re: Fwd: Re: [pnfs] problem building pnfs-nfs-utils under Fedora 13
On 05/26/2010 08:35 AM, Benny Halevy wrote:
> Has anyone successfully build pnfs enabled nfs utils under Fedora 13?
Yes... I run both the kernel and nfs-utils on a number of my test machines
to ensure they stability.
> I am running the kernel from:
> http://steved.fedorapeople.org/repos/pnfs/13/x86_64/
You might want to think about installing the yum repo at
http://steved.fedorapeople.org/pnfs.repo
so you can automatically get updates
>
> I am having trouble building these utils. I failed to generate
> 'configure' when I ran autogen.sh:
Here is the list of packages that need to be installed to
build the Fedora nfs-utils:
libgssglue-devel
libevent-devel
libcap-devel
nfs-utils-lib-devel
libtirpc-devel
libblkid-devel
openldap-devel
krb5-devel
tcp_wrappers-devel
To install these all at once, cat them into a file and then:
yum install `cat /tmp/list`
Next run the following commands:
./autogen.sh && ./configure && make
> I am new at this and would appreciate any help you can provide.
Well welcome... and please let know if there any more problems...
steved.
On 07/20/2010 10:50 PM, Sager, Mike wrote:
> Does the kernel have spnfs configured in (i.e., CONFIG_SPNFS)? Upon
> start up, spnfsd expects to find certain files under /proc/fs/spnfs. If
> spnfs isn't configured, those files won't exist.
Yes... I have the following set,
CONFIG_SPNFS=y
CONFIG_SPNFS_LAYOUTSEGMENTS=y
CONFIG_SPNFS_BLOCK=y
steved.
On Aug. 05, 2010, 0:59 +0300, "Chen, Helen Y" <[email protected]> wrote:
> Steve and Benny,
>
> Thank you very much for your help! I have successfully set up a 3-node testbed and ran some benchmark since. Unfortunately, throughput results are very poor.
>
> I am running Steve's 2.6.33.5-112.2.2.pnfs.fc13.x86_64 kernel, and exported a 28GB ramfs from my DS to the MDS. I was able to achieve ~400 MB/s over NFS using iozone. I then proceed to run the same test from the pNFS client and got only 50 MB/s. After detecting that my test data had landed on both the MDS and DS, I assumed disk I/O on the MDS was the bottleneck. So I proceeded to rebuild the kernel with CONFIG_PNFSD_LOCAL_EXPORT disabled, but achieved only 6 MB/s afterward. Is this expected, or am I doing something wrong? Please let me know if I need to provide further information.
This performance level seems unacceptable and something must have went wrong.
Were you able to get the 400 MB/s over NFSv4.1 to the MDS?
Benny
>
> Thanks,
> Helen
>
> -----Original Message-----
> From: Benny Halevy [mailto:[email protected]] On Behalf Of Benny Halevy
> Sent: Wednesday, May 26, 2010 5:36 AM
> To: [email protected]; NFS list
> Cc: Chen, Helen Y
> Subject: Fwd: Re: [pnfs] problem building pnfs-nfs-utils under Fedora 13
>
> Helen, please note that the [email protected] mailing list was deprecated.
> Forwarding to [email protected].
>
> From a quick glance I'm not sure what went wrong with your build, Steve should know better :-)
>
> Benny
>
> On May. 19, 2010, 20:32 +0300, "Chen, Helen Y" <[email protected]> wrote:
>
>
>
>
> Has anyone successfully build pnfs enabled nfs utils under Fedora 13?
> I am running the kernel from:
> http://steved.fedorapeople.org/repos/pnfs/13/x86_64/
>
> I installed libtirpc{,-devel}, tcp_wrappers{,-devel}, libevent{,-devel}, nfs-utils-lib{,-devel}, libgssglue{,-devel}, libblkid{,-devel}, and libcap{,-devel}
>
> per instructions from:
> _http://wiki.linux-nfs.org/wiki/index.php/Configuring_pNFS/spnfsd#Kernel_and_nfs-utils_compilati__on_
> <http://wiki.linux-nfs.org/wiki/index.php/Configuring_pNFS/spnfsd#Kernel_and_nfs-utils_compilation>
>
> I used libnfsidmap{,-devel} bundled in:
> Nfs-utils-lib-devel-1.1.5-1.fc13.X86_64.rpm
>
> Finally, I downloaded _nfs-utils-1.2.2-4.1.pnfs.src.rpm_
> <http://steved.fedorapeople.org/repos/pnfs/13/source/nfs-utils-1.2.2-4.1.pnfs.src.rpm>
> from _http://steved.fedorapeople.org/repos/pnfs/13/source/_
>
> I am having trouble building these utils. I failed to generate 'configure' when I ran autogen.sh:
>
> /c//leaning up ............. done
> //lobotomize//: putting auxiliary files in `.'.
> libtoolize: copying file `./ltmain.sh'
> libtoolize: putting macros in AC_CONFIG_MACRO_DIR, `aclocal'.
> libtoolize: copying file `aclocal/libtool.m4'
> libtoolize: copying file `aclocal/ltoptions.m4'
> libtoolize: copying file `aclocal/ltsugar.m4'
> libtoolize: copying file `aclocal/ltversion.m4'
> libtoolize: copying file `aclocal/lt~obsolete.m4'
> configure.ac:5: installing `./config.guess'
> configure.ac:5: installing `./config.sub'
> configure.ac:421: required file `tools/mountstats/Makefile.in' not found
> configure.ac:421: required file `tools/nfs-iostat/Makefile.in' not found/
>
> I deleted the two Makefile.in requirements from line 421 in configure.ac because there were only python scripts inside those directories.
>
> When I ran the 'configure' generated after the modification, it failed with the following output:
>
> /checking build system type... x86_64-unknown-linux-gnu checking host system type... x86_64-unknown-linux-gnu checking for a BSD-compatible install... /usr/bin/install -c checking whether build environment is sane... yes checking for gawk... gawk checking whether make sets $(MAKE)... yes checking whether to enable maintainer-specific portions of Makefiles... no checking for style of include used by make... GNU checking for gcc... gcc checking whether the C compiler works... yes checking for C compiler default output file name... a.out checking for suffix of executables...
> checking whether we are cross compiling... no checking for suffix of object files... o checking whether we are using the GNU C compiler... yes checking whether gcc accepts -g... yes checking for gcc option to accept ISO C89... none needed checking dependency style of gcc... gcc3 checking how to run the C preprocessor... gcc -E checking for grep that handles long lines and -e... /bin/grep checking for egrep... /bin/grep -E checking for ANSI C header files... no checking for sys/types.h... yes checking for sys/stat.h... yes checking for stdlib.h... no checking for string.h... yes checking for memory.h... yes checking for strings.h... yes checking for inttypes.h... yes checking for stdint.h... yes checking for unistd.h... yes checking for clnt_tli_create in -ltirpc... yes checking /usr/include/tirpc/netconfig.h usability... yes checking /usr/include/tirpc/netconfig.h presence... yes checking for /usr/include/tirpc/netconfig.h... yes checking for prctl... yes checking for cap_g
et_proc in -lcap... yes checking sys/capability.h usability... yes checking sys/capability.h presence... yes checking for sys/capability.h... yes checking for libwrap... /
>
> But libwrap is obviously installed based on the locate command:
> #locate libwrap
> /usr/lib/libwrap.so
> /usr/lib/libwrap.so.0
> /usr/lib/libwrap.so.0.7.6
> /usr/lib64/libwrap.so
> /usr/lib64/libwrap.so.0
> /usr/lib64/libwrap.so.0.7.6
>
> I am new at this and would appreciate any help you can provide.
>
> Thanks,
> Helen
>
>
>
>
>
>
>
>
>
Steve and Benny,
Thank you very much for your help! I have successfully set up a 3-node testbed and ran some benchmark since. Unfortunately, throughput results are very poor.
I am running Steve's 2.6.33.5-112.2.2.pnfs.fc13.x86_64 kernel, and exported a 28GB ramfs from my DS to the MDS. I was able to achieve ~400 MB/s over NFS using iozone. I then proceed to run the same test from the pNFS client and got only 50 MB/s. After detecting that my test data had landed on both the MDS and DS, I assumed disk I/O on the MDS was the bottleneck. So I proceeded to rebuild the kernel with CONFIG_PNFSD_LOCAL_EXPORT disabled, but achieved only 6 MB/s afterward. Is this expected, or am I doing something wrong? Please let me know if I need to provide further information.
Thanks,
Helen
-----Original Message-----
From: Benny Halevy [mailto:[email protected]] On Behalf Of Benny Halevy
Sent: Wednesday, May 26, 2010 5:36 AM
To: [email protected]; NFS list
Cc: Chen, Helen Y
Subject: Fwd: Re: [pnfs] problem building pnfs-nfs-utils under Fedora 13
Helen, please note that the [email protected] mailing list was deprecated.
Forwarding to [email protected].
>From a quick glance I'm not sure what went wrong with your build, Steve should know better :-)
Benny
On May. 19, 2010, 20:32 +0300, "Chen, Helen Y" <[email protected]> wrote:
Has anyone successfully build pnfs enabled nfs utils under Fedora 13?
I am running the kernel from:
http://steved.fedorapeople.org/repos/pnfs/13/x86_64/
I installed libtirpc{,-devel}, tcp_wrappers{,-devel}, libevent{,-devel}, nfs-utils-lib{,-devel}, libgssglue{,-devel}, libblkid{,-devel}, and libcap{,-devel}
per instructions from:
_http://wiki.linux-nfs.org/wiki/index.php/Configuring_pNFS/spnfsd#Kernel_and_nfs-utils_compilati__on_
<http://wiki.linux-nfs.org/wiki/index.php/Configuring_pNFS/spnfsd#Kernel_and_nfs-utils_compilation>
I used libnfsidmap{,-devel} bundled in:
Nfs-utils-lib-devel-1.1.5-1.fc13.X86_64.rpm
Finally, I downloaded _nfs-utils-1.2.2-4.1.pnfs.src.rpm_
<http://steved.fedorapeople.org/repos/pnfs/13/source/nfs-utils-1.2.2-4.1.pnfs.src.rpm>
from _http://steved.fedorapeople.org/repos/pnfs/13/source/_
I am having trouble building these utils. I failed to generate 'configure' when I ran autogen.sh:
/c//leaning up ............. done
//lobotomize//: putting auxiliary files in `.'.
libtoolize: copying file `./ltmain.sh'
libtoolize: putting macros in AC_CONFIG_MACRO_DIR, `aclocal'.
libtoolize: copying file `aclocal/libtool.m4'
libtoolize: copying file `aclocal/ltoptions.m4'
libtoolize: copying file `aclocal/ltsugar.m4'
libtoolize: copying file `aclocal/ltversion.m4'
libtoolize: copying file `aclocal/lt~obsolete.m4'
configure.ac:5: installing `./config.guess'
configure.ac:5: installing `./config.sub'
configure.ac:421: required file `tools/mountstats/Makefile.in' not found
configure.ac:421: required file `tools/nfs-iostat/Makefile.in' not found/
I deleted the two Makefile.in requirements from line 421 in configure.ac because there were only python scripts inside those directories.
When I ran the 'configure' generated after the modification, it failed with the following output:
/checking build system type... x86_64-unknown-linux-gnu checking host system type... x86_64-unknown-linux-gnu checking for a BSD-compatible install... /usr/bin/install -c checking whether build environment is sane... yes checking for gawk... gawk checking whether make sets $(MAKE)... yes checking whether to enable maintainer-specific portions of Makefiles... no checking for style of include used by make... GNU checking for gcc... gcc checking whether the C compiler works... yes checking for C compiler default output file name... a.out checking for suffix of executables...
checking whether we are cross compiling... no checking for suffix of object files... o checking whether we are using the GNU C compiler... yes checking whether gcc accepts -g... yes checking for gcc option to accept ISO C89... none needed checking dependency style of gcc... gcc3 checking how to run the C preprocessor... gcc -E checking for grep that handles long lines and -e... /bin/grep checking for egrep... /bin/grep -E checking for ANSI C header files... no checking for sys/types.h... yes checking for sys/stat.h... yes checking for stdlib.h... no checking for string.h... yes checking for memory.h... yes checking for strings.h... yes checking for inttypes.h... yes checking for stdint.h... yes checking for unistd.h... yes checking for clnt_tli_create in -ltirpc... yes checking /usr/include/tirpc/netconfig.h usability... yes checking /usr/include/tirpc/netconfig.h presence... yes checking for /usr/include/tirpc/netconfig.h... yes checking for prctl... yes checking for cap_ge!
t_proc in -lcap... yes checking sys/capability.h usability... yes checking sys/capability.h presence... yes checking for sys/capability.h... yes checking for libwrap... /
But libwrap is obviously installed based on the locate command:
#locate libwrap
/usr/lib/libwrap.so
/usr/lib/libwrap.so.0
/usr/lib/libwrap.so.0.7.6
/usr/lib64/libwrap.so
/usr/lib64/libwrap.so.0
/usr/lib64/libwrap.so.0.7.6
I am new at this and would appreciate any help you can provide.
Thanks,
Helen