2013-07-14 10:41 PM
I have created the Unix volume and exported to all unix client which are in the 72 subnet.
I have created the LIF on the Vserver and Ip assigned to LIF Is 192.168.72.XXX
From the Clinet(Linux Sever) which are exist in the same subnet,I m trying to mount the share which is exported from the Vserver.But i m getting below error.If any one knows about this issue.Plz help me..
[root@stglinux02 ~]# mount 192.168.72.117:/nfs /mnt
mount.nfs: access denied by server while mounting 192.168.72.117:/nfs
/nfs is the Junction-path.
Rules in the export policy is:
Clu1::> vserver export-policy rule show -vserver DataServe02 -policyname NfsPolicy
Policy Rule Access Client RO
Vserver Name Index Protocol Match Rule
------------ --------------- ------ -------- --------------------- ---------
DataServe02 NfsPolicy 1 any 192.168.72.0/255.255.255.0 any
Thanks in advace..
2013-07-15 05:00 AM
find the output below...
Clu1::> vol show -volume NFSvol -instance
Vserver Name: DataServe02
Volume Name: NFSvol
Aggregate Name: aggr2
Volume Size: 500MB
Volume Data Set ID: 1039
Volume Master Data Set ID: 2147484687
Volume State: online
Volume Type: RW
Volume Style: flex
Is Cluster-Mode Volume: true
Is Constituent Volume: false
Export Policy: NfsPolicy
User ID: 0
Group ID: 1
Security Style: unix
UNIX Permissions: ---rwxr-xr-x
Junction Path: /nfs
Junction Path Source: RW_volume
Junction Active: true
Junction Parent Volume: vol0
Available Size: 474.9MB
Filesystem Size: 500MB
Total User-Visible Size: 475MB
Used Size: 144KB
Used Percentage: 5%
Volume Nearly Full Threshold Percent: 95%
Volume Full Threshold Percent: 98%
Maximum Autosize (for flexvols only): 600MB
Autosize Increment (for flexvols only): 25MB
Minimum Autosize: 500MB
Autosize Grow Threshold Percentage: 85%
Autosize Shrink Threshold Percentage: 50%
Autosize Mode: off
Autosize Enabled (for flexvols only): false
Total Files (for user-visible data): 15182
Files Used (for user-visible data): 96
Space Guarantee Style: file
Space Guarantee in Effect: true
Snapshot Directory Access Enabled: true
Space Reserved for Snapshots: 5%
Snapshot Reserve Used: 3%
Snapshot Policy: default
Creation Time: Sat Jul 13 13:02:09 2013
Clone Volume: false
Antivirus On-Access Policy: default
Node name: Clu1-02
NVFAIL Option: off
Is File System Size Fixed: false
Extent Option: off
Reserved Space for Overwrites: 0B
Fractional Reserve: 100%
Snapshot Cloning Dependency: off
Primary Space Management Strategy: volume_grow
Read Reallocation Option: off
Inconsistency in the File System: false
Is Volume Quiesced (On-Disk): false
Is Volume Quiesced (In-Memory): false
Volume Contains Shared or Compressed Data: false
Space Saved by Storage Efficiency: 0B
Percentage Saved by Storage Efficiency: 0%
Space Saved by Deduplication: 0B
Percentage Saved by Deduplication: 0%
Space Shared by Deduplication: 0B
Space Saved by Compression: 0B
Percentage Space Saved by Compression: 0%
Block Type: 64-bit
FlexCache Connection Status: -
Is Volume Moving: false
Flash Pool Caching Eligibility: read-write
Flash Pool Write Caching Ineligibility Reason: -
Managed By Storage Service: -
Create Namespace Mirror Constituents For SnapDiff Use: -
Constituent Volume Role: -
QoS Policy Group Name: -
Is Volume Move in Cutover Phase: false
Number of Snapshot Copies in the Volume: 9
2013-07-15 05:06 AM
Does the parent volume / ...the vsroot volume have permission to traverse this mount path at vol0?
Also if ls mirrors of vsroot and you add a volume junction it won't be available until a snapmirror update since the mirror of the namespace doesn't have the new junction yet.
I also would run showmount -e ipofvserver from the Linux client.
Sent from my iPhone 5
2013-07-15 06:20 AM
A few things...
1) Showmount -e won't work. It doesn't work in cDOT yet, so don't be surprised when you get "/ everyone" as output.
2) The export policy rule client match might be incorrect. I don't think the format you have it in is correct. Pretty sure you have to specify subnet in network bit. Try this instead:
3) I don't think volume permissions have anything to do with this. The error is at mount, which means it's checking export policy rules for access to mount. If the error was access denied after mounting, then it might be vol permissions. However, it *could* possibly be an export policy rule problem at the parent volume. Check the vsroot export policy and ensure rules exist there.
4) I also don't think LS mirrors are the issue. If the issue was with a volume not showing up in the namespace, the error would be "file not found" or something similar.
Permission errors on mount are almost always export policy rule issues.
2013-07-15 07:05 AM
what is the output of the command show -instance NfsPolicy
Also try this - export-policy rule create -vserver DataServe02 -policyname NfsPolicy -clientmatch 192.168.72.0/24 -protocol nfs -rorule sys -rwrule sys -superuser sys