Bug 735547 - NFS client cant mount exported /media (tmpfs) directory
Summary: NFS client cant mount exported /media (tmpfs) directory
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: Fedora
Classification: Fedora
Component: nfs-utils
Version: 16
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Steve Dickson
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2011-09-03 12:38 UTC by Peter Lemenkov
Modified: 2011-10-29 08:16 UTC (History)
3 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2011-10-29 08:16:50 UTC


Attachments (Terms of Use)

Description Peter Lemenkov 2011-09-03 12:38:44 UTC
I just updated my home server from F-15 to F-16 and my clients (media player, apple macs and computers with Fedora) refused to mount exported /media directory. 

My configuration is quite simple - I've got several disks mounted into /media, which is exported with (ro,crossmnt,fsid=0,insecure). Unfortunately it started saying something strange now:

Sep  3 15:34:55 nostromo rpc.mountd[1320]: from_local: updating local if addr list
Sep  3 15:34:55 nostromo rpc.mountd[1320]: from_local: checked 7 local if addrs; incoming address not found
Sep  3 15:34:55 nostromo rpc.mountd[1320]: check_default: access by 192.168.1.21 ALLOWED
Sep  3 15:34:55 nostromo rpc.mountd[1320]: Received EXPORT request from 192.168.1.21.
Sep  3 15:34:58 nostromo rpc.mountd[1320]: check_default: access by 192.168.1.21 ALLOWED (cached)
Sep  3 15:34:58 nostromo rpc.mountd[1320]: Received MNT3(/media) request from 192.168.1.21
Sep  3 15:34:58 nostromo rpc.mountd[1320]: host_canonname: failed to resolve 192.168.1.21: Name or service not known
Sep  3 15:34:58 nostromo rpc.mountd[1320]: authenticated mount request from 192.168.1.21:968 for /media (/media)
Sep  3 15:34:58 nostromo rpc.mountd[1320]: nfsd_fh: inbuf '192.168.1.* 1 \x00000000'
Sep  3 15:34:58 nostromo rpc.mountd[1320]: qword_eol: fflush failed: errno 9 (Bad file descriptor)
Sep  3 15:34:58 nostromo rpc.mountd[1320]: Cannot export /media, possibly unsupported filesystem or fsid= required
Sep  3 15:34:58 nostromo rpc.mountd[1320]: nfsd_fh: found (nil) path (null)

Comment 1 Peter Lemenkov 2011-09-03 12:40:29 UTC
Just for the record - I turned off (switched to permissive mode) selinux because of other bug in recent nfs-utils.

Comment 2 Steve Dickson 2011-10-03 15:21:26 UTC

*** This bug has been marked as a duplicate of bug 739946 ***

Comment 3 Peter Lemenkov 2011-10-03 16:41:00 UTC
I'm afraid that's a different issue than bug 739946.

Comment 4 Steve Dickson 2011-10-03 18:38:05 UTC
(In reply to comment #3)
> I'm afraid that's a different issue than bug 739946.
Well you can't blame a guy for trying! 8-) 

Hmm... 

Sep  3 15:34:58 nostromo rpc.mountd[1320]: host_canonname: failed to resolve
192.168.1.21: Name or service not known

I wonder if its the same problem at this: 
https://bugzilla.redhat.com/show_bug.cgi?id=742746

Try this f16 scratch build to see if it helps
http://koji.fedoraproject.org/koji/taskinfo?taskID=3400236

Comment 5 Peter Lemenkov 2011-10-15 06:02:09 UTC
(In reply to comment #4)
> (In reply to comment #3)
> > I'm afraid that's a different issue than bug 739946.
> Well you can't blame a guy for trying! 8-) 
> 
> Hmm... 
> 
> Sep  3 15:34:58 nostromo rpc.mountd[1320]: host_canonname: failed to resolve
> 192.168.1.21: Name or service not known
> 
> I wonder if its the same problem at this: 
> https://bugzilla.redhat.com/show_bug.cgi?id=742746
> 
> Try this f16 scratch build to see if it helps
> http://koji.fedoraproject.org/koji/taskinfo?taskID=3400236

No it's not the same. If I rebind everything to the /mnt and export it (which fs isn't tmpfs) then everything works fine. If I rebind everything to the /media which fs is tmpfs) then everything stops working at the client's side.

Comment 6 Peter Lemenkov 2011-10-29 08:16:50 UTC
After several upgrades it started working again.

Just for the record - current versions of packages which could be related are:

* glibc-2.14.90-13.x86_64
* kernel-3.1.0-1.fc16.x86_64
* nfs-utils-1.2.5-1.fc16.x86_64
* selinux-policy-3.10.0-46.fc16.noarch
* selinux-policy-targeted-3.10.0-46.fc16.noarch

It still doesn't started by systemd but that's another issue definitely.


Note You need to log in before you can comment on or make changes to this bug.