- Community Home
- >
- Servers and Operating Systems
- >
- Operating Systems
- >
- Operating System - HP-UX
- >
- mountpoint issue
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
10-21-2002 09:57 AM
10-21-2002 09:57 AM
mountpoint issue
Error:
vxfs mount: /dev/vg00/lvol5 is not a vxfs filesystem.
I've tried:
1)mounting using -F vxfs
2)removing the lvol5 entry from /etc/fstab and runnign mount
3)mount to a different location
fsck -F vxfs -o full returns no errors
lvdisplay & fstyp both say it is still a vxfs filesystem.
Any ideas guys?
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
10-21-2002 10:05 AM
10-21-2002 10:05 AM
Re: mountpoint issue
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
10-21-2002 10:08 AM
10-21-2002 10:08 AM
Re: mountpoint issue
Yep, /etc/mnttab and /etc/fstab are both uncorrupted. /etc/mnttab has entries for /(root) & /stand - the 2 hfs filesystems on my hpux which do get mounted.
cheers,
Raymond.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
10-21-2002 10:18 AM
10-21-2002 10:18 AM
Re: mountpoint issue
Try running a full 'fsck' on the filesystem:
/sbin/fsck -F vxfs -y -o full /dev/vg00/lvol5
Regards!
...JRF...
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
10-21-2002 10:19 AM
10-21-2002 10:19 AM
Re: mountpoint issue
fsadm -F vxfs mountpointname
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
10-21-2002 10:43 AM
10-21-2002 10:43 AM
Re: mountpoint issue
4.
Document B3929-90007 (HP JFS 3.3
and HP OnLine JFS 3.3 Release Notes) may be worth a look although its for HPUX11.00. The vxfs version of your HPUX11i OS is most likely newer.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
10-21-2002 11:19 AM
10-21-2002 11:19 AM
Re: mountpoint issue
Check to see that your kernel has the 'vxfs' and 'vxportal' drivers present. You can look in '/stand/system' for a quick check.
JFS versions 3.0 and 3.1 used 'vxbase' and 'vxadv' instead with HP-UX 11.0.
JFS 3.3 comes with 11.11 and uses the 'vxfs' and 'vxportal' drivers.
Regards!
...JRF...
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
10-21-2002 03:14 PM
10-21-2002 03:14 PM
Re: mountpoint issue
Thanks for all the advice, unfortunately nothing seems to be helping.
***By the way, when I said the vxfs filesystems were not mountable, I meant all of them, well the good ones anyway :)
/var /opt..not even /tmp. /usr was an hfs filesystem for some reason on this machine so it's mountable.
fsadm -F vxfs /var -
vxfs fsadm: /var is not the root inode of a vxfs file sytem
/sbin/fsck -F vxfs -y -o full /dev/vg00/lvol5 - still says everything is A-okay.
I grep'd /stand/system for vx
and it returned both 'vxfs' & 'vxportal'
anymore suggestions would be greatly appreciated...
cheers,
Raymond.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
10-21-2002 04:04 PM
10-21-2002 04:04 PM
Re: mountpoint issue
# cat /etc/fstab
# fstyp -v /dev/vg00/lvol5
or any other lvol that's suppose to be vxfs. Is largefiles enabled ? If it is the mount entries in /etc/fstab file should include this option.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
10-21-2002 04:16 PM
10-21-2002 04:16 PM
Re: mountpoint issue
Can you also print out the superblock for one of the filesystems so we can check the magic number etc :
# echo "8b;p S"|fsdb -F vxfs /dev/vg00/rlvol9
super-block at 00000008.0000
magic a501fcf5 version 4
ctime 1035245203 451418 (Tue Oct 22 01:06:43 2002 BST)
log_version 9 logstart 0 logend 0
bsize 1024 size 36864 dsize 36864 ninode 0 nau 0
defiextsize 0 oilbsize 0 immedlen 96 ndaddr 10
aufirst 0 emap 0 imap 0 iextop 0 istart 0
bstart 0 femap 0 fimap 0 fiextop 0 fistart 0 fbstart 0
nindir 2048 aulen 32768 auimlen 0 auemlen 8
auilen 0 aupad 0 aublocks 32768 maxtier 15
inopb 4 inopau 0 ndiripau 0 iaddrlen 8 bshift 10
inoshift 2 bmask fffffc00 boffmask 3ff checksum e2bfa37e
free 35601 ifree 0
efree 3 3 4 1 1 3 2 0 2 2 1 0 2 1 1 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0
flags 0 mod 0 clean 3c
time 1035245319 640000 (Tue Oct 22 01:08:39 2002 BST)
oltext[0] 9 oltext[1] 16 oltsize 1
iauimlen 2 iausize 6 dinosize 256
checksum2 124
checksum3 0
Also, use kmsystem to check whether the drivers are actually in the kernel :
# kmsystem|grep vx
vxfs Y -
vxportal Y -
And for good measure, run :
# swlist -l product|grep -i vxfs
JFS B.11.11 The Base VxFS File System
OnlineJFS B.11.11 Online features of the VxFS File System
Regards,
James.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
10-21-2002 04:20 PM
10-21-2002 04:20 PM
Re: mountpoint issue
# fstyp /dev/vg00/lvolN
...will return the filesystem type. Normally, in the standard. OS filesystems only '/stand' is a hfs filesystem.
Using the filesystem type returned from the above, and translating the logical volume to its corresponding mountpoint (by using 'mount') do:
# fsadm -F vxfs /
# fsadm -F vxfs /home
...you should see 'nolargefiles' or 'largefiles'. Make sure that your '/etc/fstab' has compatible specifications, although the error reported for an inconsistency should clearly indicate this. Try mounting without using any special Online JFS options (e.g. 'mincache=direct/).
For JFS 3.3 make sure that you have a device file '/dev/vxportal'. If not, create it with:
# mknod /dev/vxportal c 97 0x000000
Make sure that you have appropriate device files with unique minor numbers corresponding to the logical volume names. You should have both character and block devices for each logical volume, like:
/dev/vg00/lvol1 64 0x000001
/dev/vg00/rlovl1 64 0x000001
Regards!
...JRF...
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
10-22-2002 01:28 AM
10-22-2002 01:28 AM
Re: mountpoint issue
I realized that if you can't mount the filesystem then using 'fsadm -F vxfs
# fstyp -v /dev/vg00/lvolN
Look at the value of 'f_flag' in the output. A value of zero (0) means "no_largefiles". A value of 16 denotes "largefiles".
Again, make sure that your '/etc/fstab' mount specifications conform with the above.
Regards!
...JRF...
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
10-23-2002 05:42 AM
10-23-2002 05:42 AM
Re: mountpoint issue
Thanks for all the advice, unfortunately I must bite the bullet and do a cold install b/c the importantance of this system is directly related to it's downtime. I'll re-install 11.00, and try the upgrade again to see if the problem repeats. I suspect the upgrade may not have updated all the filesystem components - so there were fragments of the old 11.00 system causing a conflict with the 11.11 system. If the problem repeats or I figure out what went wrong I'll post my findings. Thanks again to all who assisted me.
cheers,
Raymond.