HPE GreenLake Administration
- Community Home
- >
- Servers and Operating Systems
- >
- Operating Systems
- >
- Operating System - HP-UX
- >
- Re: problem with nfs mount
Operating System - HP-UX
1834155
Members
3081
Online
110064
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
Discussions
Forums
Discussions
back
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
Blogs
Information
Community
Resources
Community Language
Language
Forums
Blogs
Go to solution
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
04-24-2001 02:51 AM
04-24-2001 02:51 AM
Seems that the 'mount -p' on HP-UX 11.0, with NFSv3 mounted disks, produce
invalid results, i.e. - it adds the string ",NFSv3" which is invalid:
itsth104 [614]#umount /mnt
itsth104 [615]#mount infs001:/disk01/sysmgr /mnt
itsth104 [616]# mount -p | grep nfs >> /etc/fstab
itsth104 [617]#umount /mnt
itsth104 [618]#mount /mnt
nfs mount: illegal file system specific option: NFSv3
usage: mount [-l][-v|-p]
mount [-F FStype][-eQ] -a
mount [-F FStype][-eQrV][-o specific_options]
{ special | directory }
mount [-F FStype][-eQrV][-o specific_options]
special directory
itsth104 [619]#grep nfs /etc/fstab
iln001:/usr/sysmgr /usr/sysmgr nfs
defaults 0 0
iln001:/usr/common /usr/common nfs
defaults 0 0
iln001:/usr/sysmgr /usr/sysmgr nfs defaults 0 0
iln001:/usr/common /usr/common nfs defaults 0 0
infs001:/disk01/sysmgr /mnt nfs defaults,NFSv3 0 0
itsth104 [620]#sed 's/,NFSv3//' /etc/fstab
# System /etc/fstab file. Static information about the file systems
# See fstab(4) and sam(1M) for further details on configuring devices.
/dev/vg00/lvol4 / vxfs delaylog 0 1
/dev/vg00/lvol1 /stand hfs defaults 0 1
/dev/vg00/lvol3 ... swap defaults 0 0
/dev/vg00/lvol5 /afs_cache hfs defaults 0 2
/dev/vg00/lvol6 /home vxfs delaylog 0 2
/dev/vg00/lvol7 /netbatch vxfs delaylog 0 2
/dev/vg00/lvol8 /opt vxfs delaylog 0 2
/dev/vg00/lvol9 /tmp vxfs delaylog 0 2
/dev/vg00/lvol10 /usr vxfs delaylog 0 2
/dev/vg00/lvol11 /var vxfs delaylog 0 2
iln001:/usr/sysmgr /usr/sysmgr nfs
defaults 0 0
iln001:/usr/common /usr/common nfs
defaults 0 0
/dev/vg01/lvol1 /ignite_area vxfs rw,suid,largefiles,delaylog,datainlog 0 2
iln001:/usr/sysmgr /usr/sysmgr nfs defaults 0 0
iln001:/usr/common /usr/common nfs defaults 0 0
infs001:/disk01/sysmgr /mnt nfs defaults 0 0
itsth104 [621]#grep nfs /etc/fstab
iln001:/usr/sysmgr /usr/sysmgr nfs
defaults 0 0
iln001:/usr/common /usr/common nfs
defaults 0 0
iln001:/usr/sysmgr /usr/sysmgr nfs defaults 0 0
iln001:/usr/common /usr/common nfs defaults 0 0
infs001:/disk01/sysmgr /mnt nfs defaults,NFSv3 0 0
itsth104 [622]#sed 's/,NFSv3//' /etc/fstab > /tmp/fstab
itsth104 [623]#cp -f /tmp/fstab /etc/fstab
itsth104 [624]#grep nfs /etc/fstab
iln001:/usr/sysmgr /usr/sysmgr nfs
defaults 0 0
invalid results, i.e. - it adds the string ",NFSv3" which is invalid:
itsth104 [614]#umount /mnt
itsth104 [615]#mount infs001:/disk01/sysmgr /mnt
itsth104 [616]# mount -p | grep nfs >> /etc/fstab
itsth104 [617]#umount /mnt
itsth104 [618]#mount /mnt
nfs mount: illegal file system specific option: NFSv3
usage: mount [-l][-v|-p]
mount [-F FStype][-eQ] -a
mount [-F FStype][-eQrV][-o specific_options]
{ special | directory }
mount [-F FStype][-eQrV][-o specific_options]
special directory
itsth104 [619]#grep nfs /etc/fstab
iln001:/usr/sysmgr /usr/sysmgr nfs
defaults 0 0
iln001:/usr/common /usr/common nfs
defaults 0 0
iln001:/usr/sysmgr /usr/sysmgr nfs defaults 0 0
iln001:/usr/common /usr/common nfs defaults 0 0
infs001:/disk01/sysmgr /mnt nfs defaults,NFSv3 0 0
itsth104 [620]#sed 's/,NFSv3//' /etc/fstab
# System /etc/fstab file. Static information about the file systems
# See fstab(4) and sam(1M) for further details on configuring devices.
/dev/vg00/lvol4 / vxfs delaylog 0 1
/dev/vg00/lvol1 /stand hfs defaults 0 1
/dev/vg00/lvol3 ... swap defaults 0 0
/dev/vg00/lvol5 /afs_cache hfs defaults 0 2
/dev/vg00/lvol6 /home vxfs delaylog 0 2
/dev/vg00/lvol7 /netbatch vxfs delaylog 0 2
/dev/vg00/lvol8 /opt vxfs delaylog 0 2
/dev/vg00/lvol9 /tmp vxfs delaylog 0 2
/dev/vg00/lvol10 /usr vxfs delaylog 0 2
/dev/vg00/lvol11 /var vxfs delaylog 0 2
iln001:/usr/sysmgr /usr/sysmgr nfs
defaults 0 0
iln001:/usr/common /usr/common nfs
defaults 0 0
/dev/vg01/lvol1 /ignite_area vxfs rw,suid,largefiles,delaylog,datainlog 0 2
iln001:/usr/sysmgr /usr/sysmgr nfs defaults 0 0
iln001:/usr/common /usr/common nfs defaults 0 0
infs001:/disk01/sysmgr /mnt nfs defaults 0 0
itsth104 [621]#grep nfs /etc/fstab
iln001:/usr/sysmgr /usr/sysmgr nfs
defaults 0 0
iln001:/usr/common /usr/common nfs
defaults 0 0
iln001:/usr/sysmgr /usr/sysmgr nfs defaults 0 0
iln001:/usr/common /usr/common nfs defaults 0 0
infs001:/disk01/sysmgr /mnt nfs defaults,NFSv3 0 0
itsth104 [622]#sed 's/,NFSv3//' /etc/fstab > /tmp/fstab
itsth104 [623]#cp -f /tmp/fstab /etc/fstab
itsth104 [624]#grep nfs /etc/fstab
iln001:/usr/sysmgr /usr/sysmgr nfs
defaults 0 0
love computers
Solved! Go to Solution.
1 REPLY 1
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
04-24-2001 07:00 AM
04-24-2001 07:00 AM
Solution
Eran,
This is a known bug recently reported to HP, which is Service Request #8606194648 Change Reqest #JAGad63856, reported against 11.0 and 11i. The workaround for now, is to edit the /etc/fstab as you noted.
Regards,
-> Brian Hackley
This is a known bug recently reported to HP, which is Service Request #8606194648 Change Reqest #JAGad63856, reported against 11.0 and 11i. The workaround for now, is to edit the /etc/fstab as you noted.
Regards,
-> Brian Hackley
Ask me about telecommuting!
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 2025 Hewlett Packard Enterprise Development LP