Debian claims to have fixed it. Please note the following, which
suggests otherwise:
r...@noel-intrepid:~# /etc/init.d/nfs-common restart
* Stopping NFS common utilities [ OK ]
* Starting NFS common utilities [ OK ]
r...@noel-intrepid:~# lsmod | grep nfs
r...@noel-intrepid:~# mkdir /tmp/AMITOWER
r...@noel-intrepid:~# mount -t nfs4 -orsize=32768,wsize=32768 amitower.local:/
/tmp/AMITOWER
mount.nfs4: No such device
r...@noel-intrepid:~# lsmod | grep nfs
r...@noel-intrepid:~# mount -t nfs -orsize=32768,wsize=32768 amitower.local:/
/tmp/AMITOWER
r...@noel-intrepid:~# lsmod | grep nfs
nfs 308272 1
lockd 81232 1 nfs
nfs_acl 11776 1 nfs
sunrpc 229608 11 nfs,lockd,nfs_acl
r...@noel-intrepid:~# umount /tmp/AMITOWER/
r...@noel-intrepid:~# mount -t nfs4 -orsize=32768,wsize=32768 amitower.local:/
/tmp/AMITOWER
r...@noel-intrepid:~#
I believe that is sufficient to document that the bug is either back or
still present.
** Summary changed:
- (gutsy)Need to modprobe nfs module before mounting nfs4 export
+ Need to modprobe nfs module before mounting nfs4 export
** Description changed:
- Hi,
-
- I try to mount an nfs4 export but I need to modprobe the nfs module
- manually before
+ In order to mount an nfs4 export, it is necessary to modprobe the nfs
+ module manually, unless an nfs mount has already taken place.
$ sudo mount -t nfs4 router:/ /mnt
mount: unknown filesystem type 'nfs4'
$ sudo modprobe nfs
$ sudo mount -t nfs4 router:/ /mnt
- I think it's a regression from feisty
+
+ This effects gutsy (original report), hardy, intrepid and jaunty.
** Also affects: nfs-utils (Ubuntu)
Importance: Undecided
Status: New
--
Need to modprobe nfs module before mounting nfs4 export
https://bugs.launchpad.net/bugs/117957
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
[email protected]
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
