- Community Home
- >
- Servers and Operating Systems
- >
- Operating Systems
- >
- Operating System - HP-UX
- >
- Issue with mounting SERVER:...recovery/archives/CL...
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
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
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
08-26-2013 11:26 PM
08-26-2013 11:26 PM
Issue with mounting SERVER:...recovery/archives/CLIENT is causing make_net_recovery to fail.
All,
I have a very strange set of issues with NFS mounts, that are preventing IGNITE from doing it's thing. For some reason, I am able to mount /var/opt/ignite/clients with no problems, but I can't mount /var/opt/ignite/recovery/archives/CLIENT. And, the mount is hanging, rather that failing.
When I try a temporary, manual mount I have the same issue. I can, for example
# mount SERVER:/export /mnt
No problems. But when I
# mount SERVER:/var/opt/ignite/recovery/archives/CLIENT /mnt
I have no luck. The command runs, and the server sees the mount as successful (entry written to syslog by mountd), but the client does not return. I have to cancel the mount attempt with ctrl-C, and kill the orphaned mount -Fnfs process.
I actually did a tcpdump of the mount attempts(s) and it's attached below. I examined it in Wireshark, and it shows that there is a problem with it, but I can't interperet what it means. It shows that for some reason there is an error, or delay, in the NFS lookup or... something. The server is 10.40.4.21, the client is 10.40.4.22. I wonder if I don't have problems with filesystems on the server, or something; but everything looks just fine.
Any bright ideas would be appreciated.
CLIENT is a BL870i2. It's an IVM/vPars host, but that should be neither here nor there. It's interface is a hp_apa in failover mode. Each side of the failover has 1GB, interface shows as 1GB. I am also having similar troubles with same of the IVM guests.
SERVER is an rx2800i2, It's interface is a plain 1GB LOM interface, no failover. The tcpdump was captured from here, because there was something strange about tcpdump on the CLIENT (to do with promiscuous network mode, possibly because of the failover config).
Both hosts are B.11.31.1303
- Tags:
- APA
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
08-28-2013 06:53 PM
08-28-2013 06:53 PM
Re: Issue with mounting SERVER:...recovery/archives/CLIENT is causing make_net_recovery to fail.
APA is quite difficult to use with Ignite.
Here are some details:
Bill Hassell, sysadmin
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
08-29-2013 09:59 PM
08-29-2013 09:59 PM
Re: Issue with mounting SERVER:...recovery/archives/CLIENT is causing make_net_recovery to fail.
Thanks.
I think in this case that this isn't the same as the problem I have. The problem is with NFS mounts when I have sec=sys,rw=CLIENT specified.
I'm able to replicate the behaviour with a manual mount of an arbitary share with those options. More that a bit annoying.
James