Back to bug 1375259

Who When What Removed Added
Steve Dickson 2016-09-12 15:16:52 UTC Status NEW ASSIGNED
Yongcheng Yang 2016-09-13 03:52:21 UTC CC jiyin, yoyang
J. Bruce Fields 2016-10-21 16:29:19 UTC CC bfields
ChunYu Wang 2016-10-22 01:51:26 UTC CC chunwang
Steve Dickson 2016-11-21 17:14:26 UTC Blocks 1385242
Yongcheng Yang 2016-11-22 06:35:08 UTC QA Contact fs-qe yoyang
Eryu Guan 2016-11-23 03:28:47 UTC CC eguan
Steve Dickson 2016-12-07 15:27:34 UTC Keywords Patch
Steve Dickson 2016-12-07 17:29:26 UTC Summary NFSv4.1 as default NFS mount protocol NFSv4.2 as default NFS mount protocol
Steve Dickson 2016-12-07 17:54:58 UTC Status ASSIGNED MODIFIED
Fixed In Version nfs-utils-1.3.0-0.34
Trond Myklebust 2016-12-07 20:43:55 UTC CC trond.myklebust
Yongcheng Yang 2016-12-13 04:24:06 UTC CC steved
Flags needinfo?(steved)
Yongcheng Yang 2016-12-14 09:39:44 UTC See Also https://bugzilla.redhat.com/show_bug.cgi?id=1404617
Flags needinfo?(steved)
JianHong Yin 2016-12-22 02:55:59 UTC Depends On 1406885
See Also https://bugzilla.redhat.com/show_bug.cgi?id=1406885
JianHong Yin 2016-12-22 03:18:59 UTC Flags needinfo?(steved)
Steve Dickson 2017-02-23 13:52:16 UTC Flags needinfo?(steved)
Beat Rubischon 2017-02-28 10:37:42 UTC CC brubisch
Hardware Unspecified All
Yongcheng Yang 2017-03-06 06:08:23 UTC Priority unspecified high
Dave Wysochanski 2017-03-17 20:57:31 UTC CC dwysocha
Doc Type If docs needed, set a value Release Note
Yongcheng Yang 2017-03-22 07:19:54 UTC Keywords FutureFeature
errata-xmlrpc 2017-03-28 22:40:57 UTC Status MODIFIED ON_QA
Lenka Špačková 2017-04-11 15:39:41 UTC Docs Contact mnavrati
Steve Dickson 2017-05-02 17:57:57 UTC Status ON_QA ASSIGNED
Summary NFSv4.2 as default NFS mount protocol NFSv4.1 as default NFS mount protocol
Steve Dickson 2017-05-02 18:04:28 UTC Status ASSIGNED ON_QA
J. Bruce Fields 2017-05-12 21:00:24 UTC CC andros
Flags needinfo?(andros)
Yongcheng Yang 2017-05-16 02:15:03 UTC See Also https://bugzilla.redhat.com/show_bug.cgi?id=1450447
Milan Navratil 2017-05-19 14:20:10 UTC Flags needinfo?(steved)
Steve Dickson 2017-06-09 15:00:08 UTC Status ON_QA CLOSED
Resolution --- DUPLICATE
Flags needinfo?(andros) needinfo?(steved)
Last Closed 2017-06-09 11:00:08 UTC
Milan Navratil 2017-06-12 07:33:36 UTC Doc Text undefined
Doc Type Release Note No Doc Update
Steve Whitehouse 2017-06-27 13:59:10 UTC CC swhiteho
Doc Text undefined Previously, NFSv4.0 is the default NFS mount protocol. NFSv4.1 has been in the field long enough, and has significant feature improvements over NFSv4.0 such as sessions, pNFS, parallel OPENs, and session trunking that we are now making NFSv4.1 the default NFS mount protocol.

Customers who are already specifying the mount protocol minor version will not notice any difference. This change will only affect those who specify nfsv4 but without a specific minor version, and also where the server support v4.1. In case the server only supports v4.0, then the mount will remain a v4.0 mount.
Doc Type No Doc Update Release Note
Steve Whitehouse 2017-06-27 14:07:08 UTC Doc Text Previously, NFSv4.0 is the default NFS mount protocol. NFSv4.1 has been in the field long enough, and has significant feature improvements over NFSv4.0 such as sessions, pNFS, parallel OPENs, and session trunking that we are now making NFSv4.1 the default NFS mount protocol.

Customers who are already specifying the mount protocol minor version will not notice any difference. This change will only affect those who specify nfsv4 but without a specific minor version, and also where the server support v4.1. In case the server only supports v4.0, then the mount will remain a v4.0 mount.
Previously, NFSv4.0 was the default NFS mount protocol. NFSv4.1 has been in the field long enough, and has significant feature improvements over NFSv4.0 such as sessions, pNFS, parallel OPENs, and session trunking that we are now making NFSv4.1 the default NFS mount protocol.

Customers who are already specifying the mount protocol minor version will not notice any difference. This change will only affect those who specify nfsv4 but without a specific minor version, and also where the server support v4.1. In case the server only supports v4.0, then the mount will remain a v4.0 mount.

The original behaviour can be retained by specifying a minor version of 0 on the mount command line/fstab.
Steve Dickson 2017-06-27 14:52:42 UTC Doc Text Previously, NFSv4.0 was the default NFS mount protocol. NFSv4.1 has been in the field long enough, and has significant feature improvements over NFSv4.0 such as sessions, pNFS, parallel OPENs, and session trunking that we are now making NFSv4.1 the default NFS mount protocol.

Customers who are already specifying the mount protocol minor version will not notice any difference. This change will only affect those who specify nfsv4 but without a specific minor version, and also where the server support v4.1. In case the server only supports v4.0, then the mount will remain a v4.0 mount.

The original behaviour can be retained by specifying a minor version of 0 on the mount command line/fstab.
Previously, NFSv4.0 was the default NFS mount protocol. NFSv4.1 has been in the field long enough, and has significant feature improvements over NFSv4.0 such as sessions, pNFS, parallel OPENs, and session trunking that we are now making NFSv4.1 the default NFS mount protocol.

Customers who are already specifying the mount protocol minor version will not notice any difference. This change will only affect those who specify nfsv4 but without a specific minor version, and also where the server support v4.1. In case the server only supports v4.0, then the mount will remain a v4.0 mount.

The original behaviour can be retained by specifying a minor version of 0 on the mount command line/fstab/nfsmount.conf
Milan Navratil 2017-06-29 17:09:20 UTC Doc Text Previously, NFSv4.0 was the default NFS mount protocol. NFSv4.1 has been in the field long enough, and has significant feature improvements over NFSv4.0 such as sessions, pNFS, parallel OPENs, and session trunking that we are now making NFSv4.1 the default NFS mount protocol.

Customers who are already specifying the mount protocol minor version will not notice any difference. This change will only affect those who specify nfsv4 but without a specific minor version, and also where the server support v4.1. In case the server only supports v4.0, then the mount will remain a v4.0 mount.

The original behaviour can be retained by specifying a minor version of 0 on the mount command line/fstab/nfsmount.conf
NFSv4.1 is now the default NFS mount protocol

Prior to this update, NFSv4.0 was the default NFS mount protocol. NFSv4.1 provides significant feature improvements over NFSv4.0, such as sessions, pNFS, parallel OPENs, and session trunking. With this update, NFSv4.1 is the default NFS mount protocol.

If you have already specified the mount protocol minor version, this update causes no change in behavior. This update causes a change in behavior if you have specified NFSv4 without a specific minor version, provided the server supports NFSv4.1. If the server only supports NFSv4.0, the mount remains a NFSv4.0 mount. You can retain the original behavior by specifying `0` as the minor version on the mount command line in the `/fstab/nfsmount.conf` file.
Yongcheng Yang 2017-06-30 05:41:30 UTC CC mnavrati
Flags needinfo?(mnavrati)
Milan Navratil 2017-06-30 12:55:28 UTC Doc Text NFSv4.1 is now the default NFS mount protocol

Prior to this update, NFSv4.0 was the default NFS mount protocol. NFSv4.1 provides significant feature improvements over NFSv4.0, such as sessions, pNFS, parallel OPENs, and session trunking. With this update, NFSv4.1 is the default NFS mount protocol.

If you have already specified the mount protocol minor version, this update causes no change in behavior. This update causes a change in behavior if you have specified NFSv4 without a specific minor version, provided the server supports NFSv4.1. If the server only supports NFSv4.0, the mount remains a NFSv4.0 mount. You can retain the original behavior by specifying `0` as the minor version on the mount command line in the `/fstab/nfsmount.conf` file.
NFSv4.1 is now the default NFS mount protocol

Prior to this update, NFSv4.0 was the default NFS mount protocol. NFSv4.1 provides significant feature improvements over NFSv4.0, such as sessions, pNFS, parallel OPENs, and session trunking. With this update, NFSv4.1 is the default NFS mount protocol.

If you have already specified the mount protocol minor version, this update causes no change in behavior. This update causes a change in behavior if you have specified NFSv4 without a specific minor version, provided the server supports NFSv4.1. If the server only supports NFSv4.0, the mount remains a NFSv4.0 mount. You can retain the original behavior by specifying `0` as the minor version:
* on the mount command line,
* in the `/etc/fstab` file,
* or in the `nfsmount.conf` file.
Flags needinfo?(mnavrati)
Milan Navratil 2017-06-30 13:24:30 UTC Doc Text NFSv4.1 is now the default NFS mount protocol

Prior to this update, NFSv4.0 was the default NFS mount protocol. NFSv4.1 provides significant feature improvements over NFSv4.0, such as sessions, pNFS, parallel OPENs, and session trunking. With this update, NFSv4.1 is the default NFS mount protocol.

If you have already specified the mount protocol minor version, this update causes no change in behavior. This update causes a change in behavior if you have specified NFSv4 without a specific minor version, provided the server supports NFSv4.1. If the server only supports NFSv4.0, the mount remains a NFSv4.0 mount. You can retain the original behavior by specifying `0` as the minor version:
* on the mount command line,
* in the `/etc/fstab` file,
* or in the `nfsmount.conf` file.
NFSv4.1 is now the default NFS mount protocol

Prior to this update, NFSv4.0 was the default NFS mount protocol. NFSv4.1 provides significant feature improvements over NFSv4.0, such as sessions, pNFS, parallel OPENs, and session trunking. With this update, NFSv4.1 is the default NFS mount protocol.

If you have already specified the mount protocol minor version, this update causes no change in behavior. This update causes a change in behavior if you have specified NFSv4 without a specific minor version, provided the server supports NFSv4.1. If the server only supports NFSv4.0, the mount remains a NFSv4.0 mount. You can retain the original behavior by specifying `0` as the minor version:
* on the mount command line,
* in the `/etc/fstab` file,
* or in the `/etc/nfsmount.conf` file.

Back to bug 1375259