<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>NFS on Michael’s Domain</title><link>https://jeltsch.org/en/tags/nfs/</link><description>Recent content in NFS on Michael’s Domain</description><generator>Hugo</generator><language>en-us</language><copyright>Copyright © 2002 - 2026 Michael Jeltsch.</copyright><lastBuildDate>Fri, 24 Jul 2026 00:18:18 +0300</lastBuildDate><atom:link href="https://jeltsch.org/en/tags/nfs/index.xml" rel="self" type="application/rss+xml"/><item><title>Stuff the Maverick upgrade broke</title><link>https://jeltsch.org/en/stuff_the_maverick_upgrade_broke/</link><pubDate>Tue, 24 Jun 2014 00:00:00 +0000</pubDate><guid>https://jeltsch.org/en/stuff_the_maverick_upgrade_broke/</guid><description>&lt;p&gt;My 1.5 year old MacbookPro was starting to behave badly including failure to complete booting and other niceties. The computer support guy suggested to upgrade from Mountain Lion to Maverick to see whether it would fix things.Initially that seemed to work; however, many programs refuse to run under Maverick. This includes: Gnumeric and (importantly) nfs. It appears that mounting nfs via the finder is not anymore possible. However, I still am able to do it via the command line (using the resvport option, which should not be necessary, but which nevertheless does the trick):&lt;code&gt;sudo mount -o resvport -t nfs mcblserver:/var/www /Users/mjeltsch/nfs&lt;/code&gt; And talking about Gnumeric: I guess I need to compile it newly for Maverick myself…&lt;/p&gt;</description></item><item><title>How to mount a NFS export</title><link>https://jeltsch.org/en/how_to_mount_a_nfs_export/</link><pubDate>Wed, 23 May 2007 00:00:00 +0000</pubDate><guid>https://jeltsch.org/en/how_to_mount_a_nfs_export/</guid><description>&lt;p&gt;&lt;code&gt;sudo mount -t nfs -o rw server:/var/www /webserver&lt;/code&gt;or&lt;code&gt;mount server:/var/www /webserver&lt;/code&gt;The mount can be put into /etc/fstab, e.g.:&lt;code&gt;server:/var/www /webserver nfs rsize=8192,wsize=8192,timeo=14,intr,user&lt;/code&gt;This doesn&amp;rsquo;t mount the nfs export automatically during startup, but any user can mount it by executing &amp;ldquo;mount /webserver&amp;rdquo;. Be aware that if you have mounted another filesystem under /var/www (e.g. if you keep all html data on a seperate partition like /var/www/htdocs), these won&amp;rsquo;t be available unless you export the partition&amp;rsquo;s mountpoint seperately!&lt;/p&gt;</description></item><item><title>What nfs and smb shares are available on a server (showmount, smbclient)?</title><link>https://jeltsch.org/en/what_nfs_and_smb_shares_are_available_on_a_server_showmount_smbclient/</link><pubDate>Thu, 05 Apr 2007 00:00:00 +0000</pubDate><guid>https://jeltsch.org/en/what_nfs_and_smb_shares_are_available_on_a_server_showmount_smbclient/</guid><description>&lt;p&gt;The command to figure out what shares are available e.g. on the computer 192.168.0.2 type:For nfs: &lt;code&gt;/usr/sbin/showmount -e 192.168.0.2&lt;/code&gt;For samba: &lt;code&gt;smbclient -L 192.168.0.2&lt;/code&gt;&lt;/p&gt;</description></item><item><title>Exporting automounted partitions via nfs</title><link>https://jeltsch.org/en/exporting_automounted_partitions_via_nfs/</link><pubDate>Wed, 04 Apr 2007 00:00:00 +0000</pubDate><guid>https://jeltsch.org/en/exporting_automounted_partitions_via_nfs/</guid><description>&lt;p&gt;We are accessing data from our server via nfs. The nfs exports are automounted on the nfs clients&amp;rsquo; computers. It works fine. However there is a partition (a whole drive in fact) on our server that is automounted on demand. We wanted this hard drive to unmount automatically if it is not needed to save energy and reduce noise levels. When I include the mountpoint of this partition in /etc/exports everything seems to work fine, but automounting this export on a client machine fails. It can still be mounted manually though with a regular mount command. As a workaround (in order to have a desktop link in KDE to the data on the server) I did the following:
I added an entry to the fstab: &lt;code&gt;server:/automounts/multimedia /media/multimedia nfs rsize=1024,wsize=1024,noauto,user 0 0&lt;/code&gt; Then I created a shell script: &lt;code&gt;!/bin/sh mount /media/multimedia kfmclient openProfile filemanagement /media/multimedia&lt;/code&gt; Then I created a new &amp;ldquo;Link to Application&amp;rdquo;, that points to that shell script.
As a result of clicking this Link, the nfs export is mounted and a new Konqueror window opens with the contents of the mountpoint directory displayed.&lt;/p&gt;</description></item><item><title>NFS shares &amp; automount</title><link>https://jeltsch.org/en/nfs_shares_automount/</link><pubDate>Wed, 04 Apr 2007 00:00:00 +0000</pubDate><guid>https://jeltsch.org/en/nfs_shares_automount/</guid><description>&lt;p&gt;On each computer on the network there is an NFS server running, starting at bootup (edit the runlevel to enable that). In Suse Linux, NFS shares can be configured in YAST (NFS server configuration) or directly in /etc/exports file. Don&amp;rsquo;t configure the remote root to act as local root! Shares should be configured to be accessed only from the local network 192.168.0.0/24 or 192.168.0.0/255.255.255.0. &lt;code&gt;/media/downloads/ 192.168.0.0/255.255.255.0(root_squash,sync)&lt;/code&gt;UIDs have to be the same on all computers for the permissions to work properly. In case they are different you can change them in YAST. After the changes files and directories will have the old user id set as the owner, so you&amp;rsquo;ll have to change the owner globally: &lt;code&gt;chown -R --from=1001 marzena /&lt;/code&gt; Change also permissions for hidden files in the home directory: &lt;code&gt;/home/marzena chown -R --from=1001 marzena .[a-zA-Z0-9]*&lt;/code&gt;NFS shares are accessed by other computers with automount, not configured in /etc/fstab!&lt;/p&gt;</description></item></channel></rss>