Enable v4 mounts when either "nfsvers=4" or "vers=4" option are set (vers-02)
Get series with b4
b4 am [email protected]Versions newest first
- v1 Latest2 patches 29 repliesIn review
Patches in v1 No applies recorded yet
| # | Subject and files | Size | Replies | Applied |
|---|---|---|---|---|
| 1/2 | Enable v4 mounts when either "nfsvers=4" or "vers=4" option are set (vers-02)utils/ utils/ utils/ +1 more | +56 | 0 replies | |
| 2/2 | Enable v4 mounts when either "nfsvers=4" or "vers=4" option are set (vers-02)utils/ utils/ utils/ | +9 | 29 replies |
Reviews trailers per patch
No Reviewed-by, Acked-by or Tested-by trailers for v1 yet.
Cover letter [PATCH 0/2] Enable v4 mounts when either "nfsvers=4" or "vers=4" option are set (vers-02)
Here is an update of the patch I posted yesterday... It turns out the /etc/mtab was not getting updated with the correct files system type which in turn causing the remote mountd to be called on v4 mounts... So the second patch deals with that issue...
Both of these patches can be found on the "mount_vers4-r2" branch on my experiential git tree:
git://linux-nfs.org/~steved/nfs-utils-exp.git
</rant>
Why we continue to use mtab instead of /proc/mounts on umount is a bit mind boggling... plus writing to the '/etc' directory is just wrong... IMHO... espically in a read-only root environment.. </rant>
steved.