topic Re: mountpoint issue in Operating System - HP-UX

mountpoint issue

Raymond Harsaran_1 — Mon, 21 Oct 2002 16:57:50 GMT

This question may have been answered..... I recently upgraded HP-UX 11 to 11i. After reboot the vxfs filesystems were unmountable.

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?

Re: mountpoint issue

Ken Hubnik_2 — Mon, 21 Oct 2002 17:05:12 GMT

Have you checked /etc/mnttab.

Re: mountpoint issue

Raymond Harsaran_1 — Mon, 21 Oct 2002 17:08:49 GMT

Hi Ken,
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.

Re: mountpoint issue

James R. Ferguson — Mon, 21 Oct 2002 17:18:25 GMT

Hi:

Try running a full 'fsck' on the filesystem:

/sbin/fsck -F vxfs -y -o full /dev/vg00/lvol5

Regards!

...JRF...

Re: mountpoint issue

Ken Hubnik_2 — Mon, 21 Oct 2002 17:19:14 GMT

What happens when you run an fsadm command
fsadm -F vxfs mountpointname

Re: mountpoint issue

Tom Danzig — Mon, 21 Oct 2002 17:43:35 GMT

If you have an old vxfs file version, you may need to run vxupgrade. The vxupgrade command will upgrade a file system from an older disk layout to version 4. See vxupgrade(1M). However, you cannot upgrade the root (/) or /usr file systems to version
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.

Re: mountpoint issue

James R. Ferguson — Mon, 21 Oct 2002 18:19:30 GMT

Hi (again):

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...

Re: mountpoint issue

Raymond Harsaran_1 — Mon, 21 Oct 2002 22:14:39 GMT

Hey Guys,
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.

Re: mountpoint issue

S.K. Chan — Mon, 21 Oct 2002 23:04:39 GMT

Can you post the output of ..
# 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.

Re: mountpoint issue

James Murtagh — Mon, 21 Oct 2002 23:16:48 GMT

Hi,

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.

Re: mountpoint issue

James R. Ferguson — Mon, 21 Oct 2002 23:20:34 GMT

Hi (again) Raymond:

# 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...

Re: mountpoint issue

James R. Ferguson — Tue, 22 Oct 2002 08:28:46 GMT

Hi (again) Raymond:

I realized that if you can't mount the filesystem then using 'fsadm -F vxfs ' to interrogate the largefiies setting isn't going to work. Instead you can do:

# 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...

Re: mountpoint issue

Raymond Harsaran_1 — Wed, 23 Oct 2002 12:42:00 GMT

Guys,
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.