linux-nfs.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "J. Bruce Fields" <bfields@fieldses.org>
To: Kks Kbase <kks.kbase@yahoo.in>
Cc: Linux NFS <linux-nfs@vger.kernel.org>
Subject: Re: NFS exportfs options
Date: Mon, 26 Nov 2012 21:39:27 -0500	[thread overview]
Message-ID: <20121127023927.GB18930@fieldses.org> (raw)
In-Reply-To: <1353982692.94013.YahooMailNeo@web190603.mail.sg3.yahoo.com>

On Tue, Nov 27, 2012 at 10:18:12AM +0800, Kks Kbase wrote:
> Here is the command that I have used to mount.
> 
> 
> mount -f nfs 1.2.3.4:/home/nfstest1 /mnt
> 
> 
> # ls -al /mnt/
> total 28
> drwxr-xr-x  2 root root 4096 Nov 22 01:50 .

Only root is permitted to write to this directory.  But you have
root_squash turned on (which is the default; see "man export").

--b.

> drwxr-xr-x 25 root root 4096 Nov 23 20:21 ..
> -rw-r--r--  1 root root    0 Nov 22 01:50 1
> -rw-r--r--  1 root root    0 Nov 22 01:50 2
> -rw-r--r--  1 root root    0 Nov 22 01:50 3
> # ls -ld /mnt/
> drwxr-xr-x 2 root root 4096 Nov 22 01:50 /mnt/
> 
> 
> 
> Here is the output in mount command,
> 
> 1.2.3.4:/home/nfstest1 on /mnt type nfs (rw,addr=1.2.3.4)
> 
> 
> 
> 
> ----- Original Message -----
> From: J. Bruce Fields <bfields@fieldses.org>
> To: Kks Kbase <kks.kbase@yahoo.in>
> Cc: Linux NFS <linux-nfs@vger.kernel.org>
> Sent: Sunday, 25 November 2012 8:18 PM
> Subject: Re: NFS exportfs options
> 
> On Sun, Nov 25, 2012 at 12:07:13PM +0800, Kks Kbase wrote:
> > Hi,
> > 
> > Here is the mounted option on /var/lib/nfs/etab
> > 
> > # cat /var/lib/nfs/etab
> > /home/nfstest1  *(rw,sync,wdelay,hide,nocrossmnt,secure,root_squash,no_all_squash,no_subtree_check,secure_locks,no_acl,mapping=identity,anonuid=65534,anongid=65534)
> > 
> > 
> > 
> > 
> > 
> > 
> > ----- Original Message -----
> > From: Kks Kbase <kks.kbase@yahoo.in>
> > To: Linux NFS <linux-nfs@vger.kernel.org>
> > Cc: 
> > Sent: Wednesday, 21 November 2012 12:40 PM
> > Subject: NFS exportfs options
> > 
> > 
> > 
> > Hi,
> > 
> > Today I have tried to setup the NFS share. 
> > 
> > 
> > Here is the exportsfs on NFS server
> > 
> > /home/nfstest1   *(rw)
> > 
> > Then I have mounted the nfs share folder and tried to create folders and files. But I am always getting the error as permission denied either root or normal user.
> > 
> > Any ideas please?
> 
> How are you mounting this on the client?
> 
> Have you checked permissions on the exported directory?  (ls -ld
> /home/nfstest1).
> 
> --b.
> 

  reply	other threads:[~2012-11-27  2:39 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <1353479256.92520.YahooMailNeo@web190605.mail.sg3.yahoo.com>
2012-11-21  7:10 ` NFS exportfs options Kks Kbase
2012-11-25  4:07   ` Kks Kbase
2012-11-25 14:48     ` J. Bruce Fields
2012-11-27  2:18       ` Kks Kbase
2012-11-27  2:39         ` J. Bruce Fields [this message]
2012-11-27  7:37           ` Kks Kbase
2012-11-27 14:24             ` J. Bruce Fields
2012-11-28  5:02               ` Kks Kbase
2012-11-29 14:07                 ` J. Bruce Fields

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20121127023927.GB18930@fieldses.org \
    --to=bfields@fieldses.org \
    --cc=kks.kbase@yahoo.in \
    --cc=linux-nfs@vger.kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).