Created attachment 696039 [details]
/etc/fstab to show binds for nfs4export

ditto here with nfs-utils-1:1.2.7-3.fc18; downgrade to nfs-utils-1:1.2.6-14.fc18 fixes the problem

(In reply to comment #0)
> Created attachment 696038 [details]
> /etc/exports contents
> 
> Description of problem:
> 
> After upgrading from nfs-utils-1.2.6 to nfs-utils-1.2.7 clients could no
> longer see all mount points from the server. The root NFSv4 mount point is
> one of the exported filesystems (not the one designated by fsid=0 in
> /etc/exports) and other mount points do not work.
> 
> Note: this sounds like the same issue Peter had during testing of the
> package.
> 
> 
> Version-Release number of selected component (if applicable):
> nfs-utils-1.2.7-3.fc18.x86_64
> 
> 
> How reproducible:
> Always
> 
> 
> Steps to Reproduce:
> 1. Update to nfs-utils-1.2.7-3.fc18.x86_64 on server
> 2. Reboot server or just restart nfs-server.service
> 3. Trying to mount known mount point on client fails
> 4. Mounting server:/ shows wrong filesystem from server (shows
> /nfs4exports/alldata/data/ftp_mp3_root filesystem).
>   
> 
> Actual results:
> Mount points fail (e.g. server:/alldata) or show wrong filesystem on client
> (root mount, server:/, shows /nfs4exports/alldata/data/ftp_mp3_root
> filesystem).
What is the failure message?

> Expected results:
> Root mount should show other exported mount point(s) (e.g. alldata
> directory).
> Exported mount points should be mountable (i.e. server:/alldata and
> server:/alldata/data/ftp_mp3_root).
/nfs4export				*(rw,fsid=0,crossmnt)
/nfs4export/alldata			*(rw,crossmnt)
/nfs4export/alldata/data/ftp_mp3_root	*(rw,nohide)
just to be clear.... /nfs4export is a different filesystem than /nfs4export/alldata

and /nfs4export/alldata is a different filesystem as /nfs4export/alldata/data/ftp_mp3_root


> 
> Additional info:
> One mount point is automount via systemd (see fstab).

Does this still work?

I see the regression... It was caused by this commit

commit 8e2fb3fc8e46e61eeba7978a03c9fb50ff01b666
Author: NeilBrown <neilb>
Date:   Mon Dec 17 16:21:15 2012 -0500

    mountd: fix is_subdirectory to understand '/'

Looking into how to fix it...

Proposed patch:

diff --git a/utils/mountd/cache.c b/utils/mountd/cache.c
index c8aa46f..978698d 100644
--- a/utils/mountd/cache.c
+++ b/utils/mountd/cache.c
@@ -371,8 +371,11 @@ export_matches(nfs_export *exp, char *dom, char *path, struct addrinfo *ai)
 static bool subexport(struct exportent *e1, struct exportent *e2)
 {
    char *p1 = e1->e_path, *p2 = e2->e_path;
+   size_t l2 = strlen(p2);
+
    return e2->e_flags & NFSEXP_CROSSMOUNT
-       && is_subdirectory(p1, p2);
+       && strncmp(p1, p2, l2) == 0
+       && p1[l2] == '/';
 }

 struct parsed_fsid {

nfs-utils-1.2.7-4.fc18 has been submitted as an update for Fedora 18.
https://admin.fedoraproject.org/updates/nfs-utils-1.2.7-4.fc18

I hate to say that but this build doesn't fix the issue.

(In reply to comment #7)
> I hate to say that but this build doesn't fix the issue.

That's because there was typo in the spec file which caused the patch not to be applied... grrrr... nfs-utils-1.2.7-5.fc18 is on its way...

Package nfs-utils-1.2.7-5.fc18:
* should fix your issue,
* was pushed to the Fedora 18 testing repository,
* should be available at your local mirror within two days.
Update it with:
# su -c 'yum update --enablerepo=updates-testing nfs-utils-1.2.7-5.fc18'
as soon as you are able to.
Please go to the following url:
https://admin.fedoraproject.org/updates/FEDORA-2013-4396/nfs-utils-1.2.7-5.fc18
then log in and leave karma (feedback).

1.2.7-5 works for me, +ve karma left

This message is a reminder that Fedora 18 is nearing its end of life.
Approximately 4 (four) weeks from now Fedora will stop maintaining
and issuing updates for Fedora 18. It is Fedora's policy to close all
bug reports from releases that are no longer maintained. At that time
this bug will be closed as WONTFIX if it remains open with a Fedora 
'version' of '18'.

Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, simply change the 'version' 
to a later Fedora version prior to Fedora 18's end of life.

Thank you for reporting this issue and we are sorry that we may not be 
able to fix it before Fedora 18 is end of life. If you would still like 
to see this bug fixed and are able to reproduce it against a later version 
of Fedora, you are encouraged  change the 'version' to a later Fedora 
version prior to Fedora 18's end of life.

Although we aim to fix as many bugs as possible during every release's 
lifetime, sometimes those efforts are overtaken by events. Often a 
more recent Fedora release includes newer upstream software that fixes 
bugs or makes them obsolete.

Fedora 18 changed to end-of-life (EOL) status on 2014-01-14. Fedora 18 is
no longer maintained, which means that it will not receive any further
security or bug fix updates. As a result we are closing this bug.

If you can reproduce this bug against a currently maintained version of
Fedora please feel free to reopen this bug against that version. If you
are unable to reopen this bug, please file a new report against the
current release. If you experience problems, please add a comment to this
bug.

Thank you for reporting this bug and we are sorry it could not be fixed.