Skip to contentSkip to conversation

ANNOUNCE: nfs-utils-1.2.3 released.

DISCUSSION Steve Dickson 4 participants 5 messages Sep 28, 2010 – Sep 30, 2010

Subsystems (2)
lore
Share & tools
lore
#0 lore raw

New Features in this release:

* Both Client and server IPv6 support is available with the --enable-ipv6 configuration flag (which is on by default)

* NFSoverRDMA mount support.

* A large number of bug fixes.

The tarball can be found at:

http://www.kernel.org/pub/linux/utils/nfs/
http://sourceforge.net/projects/nfs

The git tree is at:
git://linux-nfs.org/nfs-utils

The change log:

http://www.kernel.org/pub/linux/utils/nfs/ChangeLog-nfs-utils-1.2.3

steved.

#1 lore raw

git://linux-nfs.org/~bhalevy/pnfs-nfs-utils.git
was rebased accordingly at tag pnfs-nfs-utils-1-2-3

Benny

Quoted 26 lines · Steve Dickson

New Features in this release:

* Both Client and server IPv6 support is available with the --enable-ipv6 configuration flag (which is on by default)

* NFSoverRDMA mount support.

* A large number of bug fixes.

The tarball can be found at:

http://www.kernel.org/pub/linux/utils/nfs/
http://sourceforge.net/projects/nfs

The git tree is at:
git://linux-nfs.org/nfs-utils

The change log:

http://www.kernel.org/pub/linux/utils/nfs/ChangeLog-nfs-utils-1.2.3

steved.
--
To unsubscribe from this list: send the line "unsubscribe linux-nfs" in the body of a message to [email protected]
More majordomo info at http://vger.kernel.org/majordomo-info.html

#2 lore raw
In reply to Steve Dickson
Quoted 8 lines · Steve Dickson

New Features in this release:

* Both Client and server IPv6 support is available with the --enable-ipv6 configuration flag (which is on by default)

* NFSoverRDMA mount support.

* A large number of bug fixes.

Unfortunately there is a new misfeature in rpc.mountd that crept in with IPv6 support.
Option '-p <port>' is no longer working, mountd succesfully registers MNT1 and then fails with -EADDRINUSE for MNT2 and MNT3 on ip4/tcp,udp and ip6/tcp,udp transports.

[root@home ~]# rpc.mountd -d all -F -p 4444 rpc.mountd: svc_tli_create: could not bind to requested address rpc.mountd: Failed to create listener xprt (mountd, 2, udp) rpc.mountd: svc_tli_create: could not bind to requested address rpc.mountd: Failed to create listener xprt (mountd, 2, tcp) rpc.mountd: svc_tli_create: could not bind to requested address rpc.mountd: Failed to create listener xprt (mountd, 2, udp6) rpc.mountd: svc_tli_create: could not bind to requested address rpc.mountd: Failed to create listener xprt (mountd, 2, tcp6) rpc.mountd: svc_tli_create: could not bind to requested address rpc.mountd: Failed to create listener xprt (mountd, 3, udp) rpc.mountd: svc_tli_create: could not bind to requested address rpc.mountd: Failed to create listener xprt (mountd, 3, tcp) rpc.mountd: svc_tli_create: could not bind to requested address rpc.mountd: Failed to create listener xprt (mountd, 3, udp6) rpc.mountd: svc_tli_create: could not bind to requested address rpc.mountd: Failed to create listener xprt (mountd, 3, tcp6) rpc.mountd: Kernel does not have pseudo root support. rpc.mountd: NFS v4 mounts will be disabled unless fsid=0 rpc.mountd: is specfied in /etc/exports file. rpc.mountd: Version 1.2.3 starting

[root@home ~]# rpcinfo -t localhost 100005
program 100005 version 1 ready and waiting

If I start mountd without '-p' it succesfully registers all versions on random ports.

[root@home ~]# rpc.mountd -d all -F
rpc.mountd: Kernel does not have pseudo root support. rpc.mountd: NFS v4 mounts will be disabled unless fsid=0 rpc.mountd: is specfied in /etc/exports file. rpc.mountd: Version 1.2.3 starting

[root@home ~]# rpcinfo -t localhost 100005
program 100005 version 1 ready and waiting
program 100005 version 2 ready and waiting
program 100005 version 3 ready and waiting

Reverting b551b1fd0052de9b8c674b30c39d9f2a1e9d79cc cures the problem. but I guess it's not the right thing to do.

Signature · 3 lines
Jan Rękorajski            |  ALL SUSPECTS ARE GUILTY. PERIOD!
baggins<at>mimuw.edu.pl   |  OTHERWISE THEY WOULDN'T BE SUSPECTS, WOULD THEY?
BOFH, MANIAC              |                   -- TROOPS by Kevin Rubio
#3 lore raw

Hi Jan-

Can you file this on bugzilla.linux-nfs.org and assign it to me? It's likely that this feature isn't working for statd either. I'll try to get right to it.

Quoted 63 lines · Jan Rękorajski
Quoted 8 lines · Steve Dickson

New Features in this release:

* Both Client and server IPv6 support is available with the --enable-ipv6 configuration flag (which is on by default)

* NFSoverRDMA mount support.

* A large number of bug fixes.

Unfortunately there is a new misfeature in rpc.mountd that crept in with IPv6 support.
Option '-p <port>' is no longer working, mountd succesfully registers MNT1 and then fails with -EADDRINUSE for MNT2 and MNT3 on ip4/tcp,udp and ip6/tcp,udp transports.

[root@home ~]# rpc.mountd -d all -F -p 4444 rpc.mountd: svc_tli_create: could not bind to requested address rpc.mountd: Failed to create listener xprt (mountd, 2, udp) rpc.mountd: svc_tli_create: could not bind to requested address rpc.mountd: Failed to create listener xprt (mountd, 2, tcp) rpc.mountd: svc_tli_create: could not bind to requested address rpc.mountd: Failed to create listener xprt (mountd, 2, udp6) rpc.mountd: svc_tli_create: could not bind to requested address rpc.mountd: Failed to create listener xprt (mountd, 2, tcp6) rpc.mountd: svc_tli_create: could not bind to requested address rpc.mountd: Failed to create listener xprt (mountd, 3, udp) rpc.mountd: svc_tli_create: could not bind to requested address rpc.mountd: Failed to create listener xprt (mountd, 3, tcp) rpc.mountd: svc_tli_create: could not bind to requested address rpc.mountd: Failed to create listener xprt (mountd, 3, udp6) rpc.mountd: svc_tli_create: could not bind to requested address rpc.mountd: Failed to create listener xprt (mountd, 3, tcp6) rpc.mountd: Kernel does not have pseudo root support. rpc.mountd: NFS v4 mounts will be disabled unless fsid=0 rpc.mountd: is specfied in /etc/exports file. rpc.mountd: Version 1.2.3 starting

[root@home ~]# rpcinfo -t localhost 100005
program 100005 version 1 ready and waiting

If I start mountd without '-p' it succesfully registers all versions on random ports.

[root@home ~]# rpc.mountd -d all -F
rpc.mountd: Kernel does not have pseudo root support. rpc.mountd: NFS v4 mounts will be disabled unless fsid=0 rpc.mountd: is specfied in /etc/exports file. rpc.mountd: Version 1.2.3 starting

[root@home ~]# rpcinfo -t localhost 100005
program 100005 version 1 ready and waiting
program 100005 version 2 ready and waiting
program 100005 version 3 ready and waiting

Reverting b551b1fd0052de9b8c674b30c39d9f2a1e9d79cc cures the problem. but I guess it's not the right thing to do.

Signature · 3 lines
Jan Rękorajski            |  ALL SUSPECTS ARE GUILTY. PERIOD!
baggins<at>mimuw.edu.pl   |  OTHERWISE THEY WOULDN'T BE SUSPECTS, WOULD THEY?
BOFH, MANIAC              |                   -- TROOPS by Kevin Rubio
Signature · 1 line
chuck[dot]lever[at]oracle[dot]com
#4 lore raw
Quoted 5 lines · Chuck Lever

Hi Jan-

Can you file this on bugzilla.linux-nfs.org and assign it to me? It's likely that this feature isn't working for statd either. I'll try to get right to it.

Done.
https://bugzilla.linux-nfs.org/show_bug.cgi?id=190

Quoted 76 lines · Jan Rękorajski
Quoted 64 lines · Steve Dickson
Quoted 9 lines

New Features in this release:

* Both Client and server IPv6 support is available with the --enable-ipv6 configuration flag (which is on by default)

* NFSoverRDMA mount support.

* A large number of bug fixes.

Unfortunately there is a new misfeature in rpc.mountd that crept in with IPv6 support.
Option '-p <port>' is no longer working, mountd succesfully registers MNT1 and then fails with -EADDRINUSE for MNT2 and MNT3 on ip4/tcp,udp and ip6/tcp,udp transports.

[root@home ~]# rpc.mountd -d all -F -p 4444 rpc.mountd: svc_tli_create: could not bind to requested address rpc.mountd: Failed to create listener xprt (mountd, 2, udp) rpc.mountd: svc_tli_create: could not bind to requested address rpc.mountd: Failed to create listener xprt (mountd, 2, tcp) rpc.mountd: svc_tli_create: could not bind to requested address rpc.mountd: Failed to create listener xprt (mountd, 2, udp6) rpc.mountd: svc_tli_create: could not bind to requested address rpc.mountd: Failed to create listener xprt (mountd, 2, tcp6) rpc.mountd: svc_tli_create: could not bind to requested address rpc.mountd: Failed to create listener xprt (mountd, 3, udp) rpc.mountd: svc_tli_create: could not bind to requested address rpc.mountd: Failed to create listener xprt (mountd, 3, tcp) rpc.mountd: svc_tli_create: could not bind to requested address rpc.mountd: Failed to create listener xprt (mountd, 3, udp6) rpc.mountd: svc_tli_create: could not bind to requested address rpc.mountd: Failed to create listener xprt (mountd, 3, tcp6) rpc.mountd: Kernel does not have pseudo root support. rpc.mountd: NFS v4 mounts will be disabled unless fsid=0 rpc.mountd: is specfied in /etc/exports file. rpc.mountd: Version 1.2.3 starting

[root@home ~]# rpcinfo -t localhost 100005
program 100005 version 1 ready and waiting

If I start mountd without '-p' it succesfully registers all versions on random ports.

[root@home ~]# rpc.mountd -d all -F
rpc.mountd: Kernel does not have pseudo root support. rpc.mountd: NFS v4 mounts will be disabled unless fsid=0 rpc.mountd: is specfied in /etc/exports file. rpc.mountd: Version 1.2.3 starting

[root@home ~]# rpcinfo -t localhost 100005
program 100005 version 1 ready and waiting
program 100005 version 2 ready and waiting
program 100005 version 3 ready and waiting

Reverting b551b1fd0052de9b8c674b30c39d9f2a1e9d79cc cures the problem. but I guess it's not the right thing to do.

Signature · 3 lines
Jan Rękorajski            |  ALL SUSPECTS ARE GUILTY. PERIOD!
baggins<at>mimuw.edu.pl   |  OTHERWISE THEY WOULDN'T BE SUSPECTS, WOULD THEY?
BOFH, MANIAC              |                   -- TROOPS by Kevin Rubio
Signature · 9 lines
chuck[dot]lever[at]oracle[dot]com




--
To unsubscribe from this list: send the line "unsubscribe linux-nfs" in
the body of a message to [email protected]
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Signature · 3 lines
Jan Rękorajski            |  ALL SUSPECTS ARE GUILTY. PERIOD!
baggins<at>mimuw.edu.pl   |  OTHERWISE THEY WOULDN'T BE SUSPECTS, WOULD THEY?
BOFH, MANIAC              |                   -- TROOPS by Kevin Rubio