GreenLake Administration
- Community Home
- >
- Servers and Operating Systems
- >
- Operating Systems
- >
- Operating System - HP-UX
- >
- Re: NFS issue
Operating System - HP-UX
1849469
Members
5829
Online
104044
Solutions
Forums
Categories
Company
Local Language
back
Forums
Discussions
Forums
- Data Protection and Retention
- Entry Storage Systems
- Legacy
- Midrange and Enterprise Storage
- Storage Networking
- HPE Nimble Storage
Discussions
Forums
Discussions
Discussions
Forums
Discussions
back
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
Discussion Boards
Blogs
Information
Community
Resources
Community Language
Language
Forums
Blogs
Topic Options
- 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
08-11-2010 10:49 AM
08-11-2010 10:49 AM
NFS issue
Trying to create a make_recovery archive, but having an NFS issue. Trying to mount the directory by hand also results in permission denied.
# /opt/ignite/bin/make_net_recovery -n 1 -A -s server
. . .
Permission denied
ERROR: Unable to mount or write server:/var/opt/ignite/recovery/archives/client
On server you may need to:
mkdir -p /var/opt/ignite/recovery/archives/client
chown bin:bin /var/opt/ignite/recovery/archives/client
If the OS on server is 11.31 or later, vi /etc/dfs/dfstab. The /etc/dfs/dfstab file on
"server" should contain the entry: "share -F nfs -o sec=sys,anon=2,rw=
/var/opt/ignite/recovery/archives/client". Where is replaced by a fully qualified client name.
After editing the /etc/dfs/dfstab file, run "shareall -F nfs"
If you need to change the owner of the directory,
you will also need to re-share the directory.
Otherwise, vi /etc/exports. The /etc/exports file on "server" should contain the entry:
"/var/opt/ignite/recovery/archives/client -anon=2,access=client".
After editing the /etc/exports file, run exportfs -av
If you need to change the owner of the directory,
you will also need to re-export the directory.
See make_net_recovery(1M) for more information.
ERROR: Failed to Create NFS mount Archive directory.
client:/var/tmp#: mount server:/var/opt/ignite/recovery/archives/bizunix /var/tmp/test1 Permission denied
# /opt/ignite/bin/make_net_recovery -n 1 -A -s server
. . .
Permission denied
ERROR: Unable to mount or write server:/var/opt/ignite/recovery/archives/client
On server you may need to:
mkdir -p /var/opt/ignite/recovery/archives/client
chown bin:bin /var/opt/ignite/recovery/archives/client
If the OS on server is 11.31 or later, vi /etc/dfs/dfstab. The /etc/dfs/dfstab file on
"server" should contain the entry: "share -F nfs -o sec=sys,anon=2,rw=
/var/opt/ignite/recovery/archives/client". Where
After editing the /etc/dfs/dfstab file, run "shareall -F nfs"
If you need to change the owner of the directory,
you will also need to re-share the directory.
Otherwise, vi /etc/exports. The /etc/exports file on "server" should contain the entry:
"/var/opt/ignite/recovery/archives/client -anon=2,access=client".
After editing the /etc/exports file, run exportfs -av
If you need to change the owner of the directory,
you will also need to re-export the directory.
See make_net_recovery(1M) for more information.
ERROR: Failed to Create NFS mount Archive directory.
client:/var/tmp#: mount server:/var/opt/ignite/recovery/archives/bizunix /var/tmp/test1 Permission denied
2 REPLIES 2
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
08-11-2010 09:52 PM
08-11-2010 09:52 PM
Re: NFS issue
Hi,
The error message is clearly telling you the solution also. Please check it.
mkdir -p /var/opt/ignite/recovery/archives/client
chown bin:bin /var/opt/ignite/recovery/archives/client
If the OS on server is 11.31 or later, vi /etc/dfs/dfstab. The /etc/dfs/dfstab file on
"server" should contain the entry: "share -F nfs -o sec=sys,anon=2,rw=
/var/opt/ignite/recovery/archives/client". Where is replaced by a fully qualified client name.
After editing the /etc/dfs/dfstab file, run "shareall -F nfs"
If you need to change the owner of the directory,
you will also need to re-share the directory.
Otherwise, vi /etc/exports. The /etc/exports file on "server" should contain the entry:
"/var/opt/ignite/recovery/archives/client -anon=2,access=client".
After editing the /etc/exports file, run exportfs -av
If you need to change the owner of the directory,
you will also need to re-export the directory.
Thanks,
Shan.
The error message is clearly telling you the solution also. Please check it.
mkdir -p /var/opt/ignite/recovery/archives/client
chown bin:bin /var/opt/ignite/recovery/archives/client
If the OS on server is 11.31 or later, vi /etc/dfs/dfstab. The /etc/dfs/dfstab file on
"server" should contain the entry: "share -F nfs -o sec=sys,anon=2,rw=
/var/opt/ignite/recovery/archives/client". Where
After editing the /etc/dfs/dfstab file, run "shareall -F nfs"
If you need to change the owner of the directory,
you will also need to re-share the directory.
Otherwise, vi /etc/exports. The /etc/exports file on "server" should contain the entry:
"/var/opt/ignite/recovery/archives/client -anon=2,access=client".
After editing the /etc/exports file, run exportfs -av
If you need to change the owner of the directory,
you will also need to re-export the directory.
Thanks,
Shan.
I am an HPE Employee

- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
08-12-2010 09:02 AM
08-12-2010 09:02 AM
Re: NFS issue
What he said.
Basically,
1. make sure the default archive path exists and has "bin:bin" permissions.
2. make sure the same path is NFS exported correctly (different method for 11.31)
Basically,
1. make sure the default archive path exists and has "bin:bin" permissions.
2. make sure the same path is NFS exported correctly (different method for 11.31)
The opinions expressed above are the personal opinions of the authors, not of Hewlett Packard Enterprise. By using this site, you accept the Terms of Use and Rules of Participation.
Company
Events and news
Customer resources
© Copyright 2026 Hewlett Packard Enterprise Development LP