- Community Home
- >
- Servers and Operating Systems
- >
- Operating Systems
- >
- Operating System - HP-UX
- >
- Ignite and 2 GIG file
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
Forums
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
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
03-10-2004 02:53 AM
03-10-2004 02:53 AM
Ignite and 2 GIG file
Any ideas ?
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
03-10-2004 02:57 AM
03-10-2004 02:57 AM
Re: Ignite and 2 GIG file
You don't mention the OS of the Ignite Server.
The fix is to install version 3 of NFS from your applications cd or from itrc.hp.com patches.
That will at least deal with the error message at hand.
SEP
Owner of ISN Corporation
http://isnamerica.com
http://hpuxconsulting.com
Sponsor: http://hpux.ws
Twitter: http://twitter.com/hpuxlinux
Founder http://newdatacloud.com
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
03-10-2004 03:01 AM
03-10-2004 03:01 AM
Re: Ignite and 2 GIG file
Try it by setting
AUTOFS=1
in /etc/rc.config.d/nfsconf
You'll need to bounce nfs
/sbin/init.d/nfs.client stop
/sbin/init.d/nfs.server stop
I always kill the automounter for good measure with a ps -ef and kill the PID
then
/sbin/init.d/nfs.server start
/sbin/init.d/nfs.sclient start
Regards,
Dave.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
03-10-2004 03:04 AM
03-10-2004 03:04 AM
Re: Ignite and 2 GIG file
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
03-10-2004 03:08 AM
03-10-2004 03:08 AM
Re: Ignite and 2 GIG file
I'm not sure whether NFS 3.0 was released for that OS, but will say probably yes.
To solve this problem you must upgrade NFS.
Your OS if course is 9 months past its support date. If this is a production system that needs support, the time is present to find a way to migrate.
SEP
Owner of ISN Corporation
http://isnamerica.com
http://hpuxconsulting.com
Sponsor: http://hpux.ws
Twitter: http://twitter.com/hpuxlinux
Founder http://newdatacloud.com
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
03-10-2004 03:24 AM
03-10-2004 03:24 AM
Re: Ignite and 2 GIG file
if upgrading the OS is not an option, I considered upgrading 10.20 to NFS V3 for a similar scenario, here are my notes:
*****************************
procedure used to upgrade NFS (Network File System) version 2 to NFS version 3 at HP-UX 10.20
1. Create the following directories and touch the following files:
mkdir /sbin/fs/autofs
mkdir /sbin/fs/cachefs
touch /sbin/fs/autofs/mount
touch /sbin/fs/cachefs/mount
Note: NFS uses these files to determine if PV2 code or PV3 code should be installed.
If the mount files already exist under autofs and cachefs:
A. Remove the files.
B. touch the files so that they will be null.
2. Create a swdepot and download the appropriate set of patches
(Series 700 system or Series 800 system) into the depot
Series 800 System
PHKL_8694 sys/time.h fix for select(2)/C++ defects
PHCO_10947 libHcurses cumulative patch
PHCO_14645 libc cumulative header file patch
PHNE_15159 nsswitch.conf patch for automounter
PHKL_15247 kernel header files cumulative patch
PHCO_15262 find(1) cumulative patch
PHCO_15263 chmod(1) cumulative patch
PHCO_15336 tar(1) cumulative patch
PHCO_15339 fsclean(1M) support for NFSv3 cum. patch
PHCO_15340 /sbin/is_local_root NFSv3 support cum. patch
PHCO_15341 mountall(1M) with NFSv3 CacheFS cum. patch
PHCO_15343 umountall(1M) with NFSv3 support cum. patch
PHCO_16591 fsck_vxfs(1M) cumulative patch
PHKL_16751 SIG_IGN/SIGCLD,LVM,JFS,PCI/SCSI cumulative patch
PHCO_16809 du(1) cumulative patch
PHCO_16874 umount(1M) cumulative patch
PHKL_16957 Physical dump devices configuration patch
PHKL_17574 ki/nfs, vasusage, ACE 2 bundle cumulative patch
PHCO_17635 Release Notes cumulative patch (HWE 3.0)
PHKL_17858 Fix for mount/access of disc sections
PHCO_18563 LVM commands cumulative patch
PHNE_19299 NetTL, Nettladm cumulative patch
PHNE_19936 cumulative ARPA Transport patch
PHCO_20061 mount(1M) cumulative patch
PHCO_20441 libc cumulative patch
PHKL_20611 Correct process hangs on ufs inodes
PHNE_20957 NFS Kernel General Rel & Perf Patch
PHCO_21263 fbackup(1M)/frecover(1M) cumulative patch
PHNE_21375 NFS/NIS cumulative megapatch
PHKL_21595 VxFS (JFS) mount, fsck cumulative patch
PHKL_21661 lo_realvfs panic fix, Cumulative LOFS patch
PHNE_21904 LAN products cumulative Patch
PHCO_22273 bdf(1M) cumulative patch
PHCO_22275 df(1M) cumulative patch
Note: These patches, as with any patches, may be superseded.
Please check for the latest patches at the IT Resource
Center (ITRC)
*****************************
Regards,
Bernhard