After having successfully updated to sys-apps/util-linux-2.13, I found my system not being able to mount any nfs shared filesystem anymore. After having restored the /bin/mount command from the previous util-linux-2.12r-r7 version, I am perfectly able to mount NFS shared filesystems anymore. Reproducible: Always Steps to Reproduce: 1.install sys-apps/util-linux-2.13 2. try 'mount -t nfs server:/directory /mountpoint' 3. see your system bailing out with an error Actual Results: uranus bin # mount -t nfs mars:/usr/portage /usr/portage mount: wrong fs type, bad option, bad superblock on mars:/usr/portage, missing codepage or other error In some cases useful info is found in syslog - try dmesg | tail or so Expected Results: It should have mounted the NFS directory as expected. the version information for the mount command says: uranus bin # mount --version mount (util-linux-ng 2.13) When using the old mount command, everything succeeds: uranus bin # mount_old --version mount: mount-2.12r uranus bin # mount_old -t nfs mars:/usr/portage /usr/portage uranus bin #
/usr/share/doc/util-linux-2.13/v2.13-ReleaseNotes Release highlights: ------------------ mount(8) doesn't include NFS client code anymore. Don't forget to install nfs-utils 1.1.0 or newer with /sbin/[u]mount.{nfs,nfs4}.
Ideally, this should be something for the GWN so that users aren't hit unknowing. I am going to CC them so that they are aware..I hope I haven't done anything wrong....
Thanks for the information about nfs-utils 1.1.0 being required. However, IMHO the new util-linux-2.13 should make sure that nfs-utils 1.1.0 are installed (via masking against the older version or something like that). Simply allowing to install the newer util-linux versions with older nfs-utils versions are clearly calling for trouble IMHO.
Can I add a heartfelt plea for, at the very least, an ewarn message stating that nfs-utils is now required. After an upgrade involving several packages, I lost the ability to mount NFS shares (including my portage directories) with absolutely no indication of which may be the culpable package. The solution in Comment 3 wouldn't have helped as this system did not have nfs-utils installed. Maybe a nfs USE flag creating a dependency on >=nfs-utils-1.1.0 would ease the transition, especially when these packages go stable.
*** Bug 191173 has been marked as a duplicate of this bug. ***
I'm sorry to destroy the party but this bug is not resolved. I have the same problem but I have net-fs/nfs-utils-1.1.0-r1 installed and mount.nfs is present still though I get the same error and am unable to connect to my shares. sys-apps/util-linux-2.12r-r7 net-fs/nfs-utils-1.1.0-r1 I re-emerged sys-apps/util-linux-2.12r-r7 as mentioned in the first comment but it didn't help. The system can't be brought back to mount nfs shares anymore.
(In reply to comment #6) > I'm sorry to destroy the party but this bug is not resolved. Then move this out of this bug because your problem is off-topic here.
Just a quick note regarding not-working NFS mounts even when all the latest packages are installed. The new nfs-utils seem to need a mount option telling them to use a certain NFS version, otherwise they only try NFS version 3. The old util-linux didn't need this. Use -o nfsvers=2 for NFS version 2 and -t nfs4 for NFS version 4. This solution works at our site where we use NFS version 2.
