Re: NFS issues

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



Yes, mount command seems fine to me. What does this command say

mount -t nfs,_netdev 192.168.1.14:/home/magnusg/Music /home/magnusg/Music

--Soham

On Sun, Oct 23, 2011 at 5:12 AM, Gerhard Magnus <magnus@xxxxxxxxxxxxxxx> wrote:

> On 10/23/2011 07:24 AM, Gerhard Magnus wrote:
> > I have a small home LAN. I am running FC15 on the server. As I still
> > have not made a full peace with FC15 I'm still running FC13 on the
> > client. Several years and FC versions ago, someone on the list told me
> > about this procedure for setting up NFS, which has been working fine...
> > until now.

> > --------------------
> >
> > On the server (192.168.1.14):
> > My /etc/exports file looks like this:
> > /home/magnusg/Music
> > 192.168.1.12,192.168.1.13(rw,insecure,sync,nohide)
> > Using the system-config-nfs "General Options tab" I have "Allow
> > connections from port 1024 and higher" checked.
> > I have services nfs and nfslock running on levels 3,4,5.
> > In /etc/sysconfig/nfs I've set these ports:
> > RQUOTAD_PORT=4000
> > LOCKD_TCPPORT=4001
> > LOCKD_UDPPORT=4001
> > MOUNTD_PORT=4002
> > STATD_PORT=4003
> > In the firewall I have these ports open:
> > NFSV4 2049 (tcp)
> > 4000-4003 (tcp and udp)
> > 111 (tcp and udp)
> > --------------------
> > on the client (192.168.1.13):
> > I added this to /etc/fstab:
> > 192.168.1.14:/home/magnusg/Music    /home/magnusg/Music    nfs
> > rw,auto,hard,intr,bg      0 0
> > Services netfs, nfslock and rpcbind are running on levels 3,4,5.
> > --------------------
> > When I boot the client and get to the "Mounting NFS filesystems" section
> > I don't get error messages -- but I do see this:
> > mount.nfs: backgrounding 192.168.1.14:/home/magnusg/Music
> > : mount options
> > "hard,intr,bg,vers=4,addr=192.168.1.14,clientaddr=192.168.1.13"
> > Then I don't get a "Music" icon on my desktop, and when I open the
> > folder there's nothing in it.

On Sun, 2011-10-23 at 07:32 +0800, Ed Greshko wrote
> You may be running into the same bug others have....  That is NFS
mounts
> not mounting at boot time.  There is a bugzilla open for it....
> https://bugzilla.redhat.com/show_bug.cgi?id=692008
>
> Try mounting manually.  If that works, then you're experiencing the
bug.

Is this the right mount command?
mount -t nfs 192.168.1.14:/home/magnusg/Music /home/magnusg/Music

I get this error message:
mount.nfs: Connection timed out

-- 
users mailing list
users@xxxxxxxxxxxxxxxxxxxxxxx
To unsubscribe or change subscription options:
https://admin.fedoraproject.org/mailman/listinfo/users
Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines
[Index of Archives]     [Older Fedora Users]     [Fedora Announce]     [Fedora Package Announce]     [EPEL Announce]     [EPEL Devel]     [Fedora Magazine]     [Fedora Summer Coding]     [Fedora Laptop]     [Fedora Cloud]     [Fedora Advisory Board]     [Fedora Education]     [Fedora Security]     [Fedora Scitech]     [Fedora Robotics]     [Fedora Infrastructure]     [Fedora Websites]     [Anaconda Devel]     [Fedora Devel Java]     [Fedora Desktop]     [Fedora Fonts]     [Fedora Marketing]     [Fedora Management Tools]     [Fedora Mentors]     [Fedora Package Review]     [Fedora R Devel]     [Fedora PHP Devel]     [Kickstart]     [Fedora Music]     [Fedora Packaging]     [Fedora SELinux]     [Fedora Legal]     [Fedora Kernel]     [Fedora OCaml]     [Coolkey]     [Virtualization Tools]     [ET Management Tools]     [Yum Users]     [Yosemite News]     [Gnome Users]     [KDE Users]     [Fedora Art]     [Fedora Docs]     [Fedora Sparc]     [Libvirt Users]     [Fedora ARM]

  Powered by Linux