- Community Home
- >
- Storage
- >
- Midrange and Enterprise Storage
- >
- HPE 3PAR StoreServ Storage
- >
- Re: 3PAR NFS file share permission
Categories
Company
Local Language
Forums
Discussions
Forums
- Data Protection and Retention
- Entry Storage Systems
- Legacy
- Midrange and Enterprise Storage
- Storage Networking
- HPE Nimble Storage
Discussions
Discussions
Discussions
Forums
Forums
Discussions
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
- BladeSystem Infrastructure and Application Solutions
- Appliance Servers
- Alpha Servers
- BackOffice Products
- Internet Products
- HPE 9000 and HPE e3000 Servers
- Networking
- Netservers
- Secure OS Software for Linux
- Server Management (Insight Manager 7)
- Windows Server 2003
- Operating System - Tru64 Unix
- ProLiant Deployment and Provisioning
- Linux-Based Community / Regional
- Microsoft System Center Integration
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Community
Resources
Forums
Blogs
- Subscribe to RSS Feed
- Mark Topic as New
- Mark Topic as Read
- Float this Topic for Current User
- Bookmark
- Subscribe
- Printer Friendly Page
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО11-16-2017 09:32 PM
тАО11-16-2017 09:32 PM
3par NFS file share permission
Hi,
I have a question in 3par file persona NFS file share. Environment: 3par 20800, OS 3.2.2MU4
After I completed the file persona, VFS, fstore, fshare configuration. I tried the client(RHEL 6.3) access. Seems that there are three NFS shares that I can see from the client. What is the /nfsshares? Where is it from?
And, I tried to mount the /NFS1/NFS1/test/3partest, the root user is always squashed to nobody(UID=99), and other users in the client cannot access the mount point.
But when mounting the /nfsshares/NFS1/NFS1/test/3partest, the root user and other users in the client can have theire own UID/GID when access the mount point.
So I cannot understand what is the /nfsshare directory, I didn't define it in the file persiona creation. And which path should I mount from the client? Thanks for the help
#############
[root@crmsvrd ~]# showmount -e 172.18.208.218
Export list for 172.18.208.218:
/nfsshares *
/NFS1/NFS1/test/3partest 172.18.95.137
/nfsshares/NFS1/NFS1/test/3partest 172.18.95.137
SS20800 cli% showfshare nfs -d
Share Name : 3partest
File Provisioning Group : NFS1
Virtual File Server : NFS1
File Store : test
Share Directory : 3partest
Full Directory Path : /NFS1/NFS1/test/3partest
State : normal
Clients : 172.18.95.137
Options : subtree_check, sync, hide, crossmnt, no_root_squash, sec=sys, no_all_squash, no_wdelay, secure, auth_nlm, rw
Comment : ---
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО11-18-2017 08:40 PM
тАО11-18-2017 08:40 PM
Re: 3PAR NFS file share permission
Have you looked at creating FP users and groups, to match your Linux user IDs?
showfsuser and showfsgroup
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО12-21-2018 10:26 AM
тАО12-21-2018 10:26 AM
Re: 3par NFS file share permission
Did you ever find a solution for this? It seems like /nfsshares is some kind of internal use only setting, or debug setting, that was never turned off. However, I don't know.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО12-22-2018 05:20 AM
тАО12-22-2018 05:20 AM
Re: 3par NFS file share permission
The "/nfsshares" directory that you can see if you run a "showmount -e" against the FilePersona Appliance, is the root of the so called NFSv4-Pseudo-filesystem. This is design and feauture of NFSv4.x.
All exported NFS-shares are automatically bound into the pseudo-filesystem, so that a NFSv4 client can travers them (if not restricted by the exports)
Note that "/nfsshare" always exist, even if you have not created a single nfs-share.
Clients that are not allowed to access a NFS-share will be able to see the share, but not allowed to enter it.