This bug still exists in mount 2.13~rc3-5 with kernel 2.6.22-10-generic, i.e. Gutsy as client. It's easy to reproduce this bug: server IP address: 192.168.120.254 client IP address: 192.168.120.170
0. In nfs server, mkdir 2 directories mkdir -p /tftpboot/opt /opt The /etc/exports is: /tftpboot 192.168.120.170(ro,sync,async,no_root_squash,subtree_check) /opt 192.168.120.170(ro,sync,async,no_root_squash,subtree_check) Then run "/etc/init.d/nfs-kernel-server start" to export them. 1. In the client, mount the directories from the nfs server: [gutsy]~>mount -t nfs 192.168.120.254:/tftpboot /mnt [gutsy]~>mount -t nfs 192.168.120.254:/opt/ /mnt/opt/ [gutsy]~>mountpoint /mnt/opt/ /mnt/opt/ is not a mountpoint The contents of /proc/mounts ------------------ [gutsy]~>cat /proc/mounts rootfs / rootfs rw 0 0 none /sys sysfs rw,nosuid,nodev,noexec 0 0 none /proc proc rw,nosuid,nodev,noexec 0 0 udev /dev tmpfs rw 0 0 /dev/mapper/gutsy-root / ext3 rw,data=ordered 0 0 /dev/mapper/gutsy-root /dev/.static/dev ext3 rw,data=ordered 0 0 tmpfs /var/run tmpfs rw,nosuid,nodev,noexec 0 0 tmpfs /var/lock tmpfs rw,nosuid,nodev,noexec 0 0 tmpfs /lib/modules/2.6.22-10-generic/volatile tmpfs rw 0 0 tmpfs /dev/shm tmpfs rw 0 0 devpts /dev/pts devpts rw 0 0 fusectl /sys/fs/fuse/connections fusectl rw 0 0 tmpfs /var/run tmpfs rw,nosuid,nodev,noexec 0 0 tmpfs /var/lock tmpfs rw,nosuid,nodev,noexec 0 0 /dev/sda1 /boot ext3 rw,data=ordered 0 0 securityfs /sys/kernel/security securityfs rw 0 0 nfsd /proc/fs/nfsd nfsd rw 0 0 192.168.120.254:/tftpboot /mnt nfs rw,vers=3,rsize=32768,wsize=32768,hard,proto=tcp,timeo=600,retrans=2,sec=sys,addr=192.168.120.254 0 0 192.168.120.254:/opt/ /mnt/opt nfs rw,vers=3,rsize=32768,wsize=32768,hard,proto=tcp,timeo=600,retrans=2,sec=sys,addr=192.168.120.254 0 0 ------------------------ Apparently, the command mountpoint gave the wrong result. The weird thing is, if I replace the /tftpboot with other name in the above steps, like /work, this problem does NOT exist. It's only for /tftpboot ? -- mountpoint failed to identify some NFS mount point as mount point https://bugs.launchpad.net/bugs/93634 You received this bug notification because you are a member of Ubuntu Bugs, which is the bug contact for Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
