Advertisement

07.07.2008 at 09:28PM PDT, ID: 23545478
[x]
Attachment Details
[x]
The Solution Rating System

With so many solutions, how can you tell which solutions are most likely to help you and which ones are not? To provide you with a tool to use, we rate our solutions based on various elements that most accurately determine if a solution is a quality solution. To explain what factors affect the solution rating, here are the elements we take into consideration when formulating our solution rating.

  • The Grade of the Solution
  • The Zone Rank of the Expert Providing the Solution
  • The Number of Author and Expert Comments
  • The Number of Experts Contributing
  • The Feedback of the Community

Your Input Matters
Because of the way the system is set up, the most important variable in this equation is you. As a member of Experts Exchange, you are able to cast your vote on the quality of the solutions in regard to how complete, accurate, helpful and easy to understand each solution is. When you provide your feedback, each rating is adjusted accordingly. So, if you see a solution that has a poor rating that you think is a good solution, let us know by rating it. As you do, the rating will be adjusted and will become more accurate for other members of our site.

If you have any suggestions that you would like to make for our rating system, please ask a question in the Suggestions Zone of Community Support.

Thank you!
9.2

Setting up NFS between 2 Ubuntu 8.04 desktops - mount.nfs: internal error

Asked by pkutter in NFS File Server, Linux Administration, Ubuntu

Tags: , , ,

When attempting to mount the NFS share on the client machine I receive the following -
sudo mount /media/Media
mount.nfs:internal error

The volume that I am trying to mount is about 3 TB. It was a little bit of trouble getting this to be mounted on the local file system a few months back. Is there any limitations on volume size for NFS?

I configured NFS by following this tutorial
http://ubuntuforums.org/showthread.php?s=c173c3d120b03d1a4e5879e4164123aa&t=249889&page=6

The only thing that I wasn't quite sure about is if I had the directories in fstab configured correctly on the client can anyone verify this?

Firewalls are off on both machines.

The client machine can access samba shares on the server just fine, so the network config should be ok.

Contents of /etc/exports on server

/media/3tbarray/Media 10.10.10.0/24(ro,async)



Contents of /etc/default/portmap on server

# Portmap configuration file
#
# Note: if you manually edit this configuration file,
# portmap configuration scripts will avoid modifying it
# (for example, by running 'dpkg-reconfigure portmap').

# If you want portmap to listen only to the loopback
# interface, uncomment the following line (it will be
# uncommented automatically if you configure this
# through debconf).
#OPTIONS="-i 127.0.0.1"

results of ifconfig -a on server (this looks funny because I am running virtualbox with a static IP address configured by following zdude's post from February 27th, 2007 - http://ubuntuforums.org/showthread.php?s=4aa0e45db970b99270446bd66b55386a&t=346185&highlight=Failed+to+initialize+Host+Interface+Networking.&page=4

 ifconfig -a
eth1      Link encap:Ethernet  HWaddr 00:1d:7d:d6:62:f7  
          inet6 addr: fe80::21d:7dff:fed6:62f7/64 Scope:Link
          UP BROADCAST RUNNING PROMISC MULTICAST  MTU:1500  Metric:1
          RX packets:125543392 errors:0 dropped:0 overruns:0 frame:0
          TX packets:110232027 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1000
          RX bytes:3445788209 (3.2 GB)  TX bytes:166279067 (158.5 MB)
          Interrupt:222 Base address:0x6000

lo        Link encap:Local Loopback  
          inet addr:127.0.0.1  Mask:255.0.0.0
          inet6 addr: ::1/128 Scope:Host
          UP LOOPBACK RUNNING  MTU:16436  Metric:1
          RX packets:460256 errors:0 dropped:0 overruns:0 frame:0
          TX packets:460256 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:0
          RX bytes:348495487 (332.3 MB)  TX bytes:348495487 (332.3 MB)

tap0      Link encap:Ethernet  HWaddr 00:ff:c4:d7:d7:66  
          inet6 addr: fe80::2ff:c4ff:fed7:d766/64 Scope:Link
          UP BROADCAST RUNNING PROMISC MULTICAST  MTU:1500  Metric:1
          RX packets:185765826 errors:0 dropped:0 overruns:0 frame:0
          TX packets:151643263 errors:0 dropped:36 overruns:0 carrier:0
          collisions:0 txqueuelen:500
          RX bytes:1556372563 (1.4 GB)  TX bytes:513584808 (489.7 MB)

umlbridge Link encap:Ethernet  HWaddr 00:1d:7d:d6:62:f7  
          inet addr:10.10.10.249  Bcast:10.10.10.255  Mask:255.255.255.0
          inet6 addr: fe80::5cc1:e5ff:fe2f:74a7/64 Scope:Link
          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
          RX packets:107422917 errors:0 dropped:0 overruns:0 frame:0
          TX packets:57979534 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:0
          RX bytes:2524716056 (2.3 GB)  TX bytes:3661297336 (3.4 GB)



relevant contents of /etc/fstab on client

10.10.10.249:/media/3tbarray/Media /media/Media nfs rsize=8192,wsize=8192,timeo=14,intr



Start Free Trial
[+][-]07.08.2008 at 09:32PM PDT, ID: 21960625

View this solution now by starting your 7-day free trial. Setting up your free trial is quick, easy, and secure. We will return you to this solution, unlocked, when you're done.

 

About this solution

Zones: NFS File Server, Linux Administration, Ubuntu
Tags: Ubuntu, Ubuntu 8.04 Desktop, 8.04, mount.nfs: internal error
Sign Up Now!
Solution Provided By: LinuxNtwrkng
Participating Experts: 1
Solution Grade: A
 
 
[+][-]07.08.2008 at 10:17PM PDT, ID: 21960761

Often, when Experts are collaborating with members who have asked questions, they will request additional information about the problem. Askers respond with an author comment like this one.

Start your 7-day free trial to view this Author Comment or ask the Experts your question.

 
 
Loading Advertisement...
20080716-EE-VQP-32 / EE_QW_2_20070628