Quick Review: Boxee Box
December 27, 2011 – 12:22 am | 3 Comments

Some of the technical issues with Boxee Box could have been fixed if the dev team was paying more attention to addressing the bugs rather than adding “features” of dubious value. In the final analysis, for the price and ease of use, Boxee Box is the best in its class and price range. You just need to be mindful of its limitations and buy it in hope of future improvements to its usability.

Read the full story »
Networking

Unix and Linux network configuration. Multiple network interfaces. Bridged NICs. High-availability network configurations.

Applications

Reviews of latest Unix and Linux software. Helpful tips for application support admins. Automating application support.

Data

Disk partitioning, filesystems, directories, and files. Volume management, logical volumes, HA filesystems. Backups and disaster recovery.

Monitoring

Distributed server monitoring. Server performance and capacity planning. Monitoring applications, network status and user activity.

Commands & Shells

Cool Unix shell commands and options. Command-line tools and application. Things every Unix sysadmin needs to know.

Home » Commands & Shells, Filesystems, Networking

NFS “Not Owner” Error

Submitted by on August 30, 2010 – 11:34 pmOne Comment
NFS “Not Owner” Error

The “not owner” error is displayed on the client system (usually Solaris) when attempting to mount an NFS share from a server. This error may appear even though the share is correctly exported and the client system has full access. If you are getting a “permission denied” error, then this article is not for you and you should check here instead.

The “not owner” error is likely when the server is running NFS v. 4 and the client is running NFS v. 3 or an earlier release of v. 4. This error sometimes also appears when the NFS server is a Linux system and the client system is running Solaris.

To resolve the problem:

  1. edit /etc/default/nfs (this location is for Solaris; for other operating environments just do a search for a file called “nfs” in /etc) on the client system
  2. modify or add the following line: NFS_CLIENT_VERSMAX=3
  3. save the file and attempt to mount the share again. You do not need to restart NFS. You may need to restart automounter, if that is what you are using.

The above change will force the client to use NFS v. 3, which at the moment is more widely-compatible than version four. This should not cause any problems for the NFS server or other clients.

Popularity: 1% [?]

Related posts:

  1. NFS-mount “Permission denied” error
  2. DownThemAll! “No free space” error
  3. Forcing Linux to Reboot
  4. Create and mount ISO image under Solaris

One Comment »

Leave a comment!

Add your comment below, or trackback from your own site. You can also subscribe to these comments via RSS.

Be nice. Keep it clean. Stay on topic. No spam.

You can use these tags:
<a href="" title=""> <abbr title=""> <acronym title=""> <b> <blockquote cite=""> <cite> <code> <del datetime=""> <em> <i> <q cite=""> <strike> <strong> <pre lang="" line="" escaped="" highlight="">

This is a Gravatar-enabled weblog. To get your own globally-recognized-avatar, please register at Gravatar.