Associating the mount point with the device file

[Fay_1]

My hpux system has the following mount points
# mount
/ on /dev/root log on Tue Feb 19 12:41:08 2002
/stand on /dev/vg00/lvol1 defaults on Tue Feb 19 12:41:11 2002
/var on /dev/vg00/lvol8 delaylog,nodatainlog on Tue Feb 19 12:41:20 2002
/usr on /dev/vg00/lvol7 delaylog,nodatainlog on Tue Feb 19 12:41:21 2002
/tmp on /dev/vg00/lvol4 delaylog,nodatainlog on Tue Feb 19 12:41:21 2002
/opt on /dev/vg00/lvol6 delaylog,nodatainlog on Tue Feb 19 12:41:21 2002
/home on /dev/vg00/lvol5 delaylog,nodatainlog on Tue Feb 19 12:41:21 2002

For the device file that belongs to vg00, I can find the device file that these mount points are mounting to using vgdisplay. But the first mount point / on /dev/root, I don't know where that come from. Doing a ll /dev/root, I get

ll /dev/root
brw-r----- 1 bin sys 255 0xffffff Feb 26 16:25 /dev/root

How do I konw what device(/dev/rdsk/c?t?d?) this mount point is mounting to?

Thanks!

[Michael Tully · Accepted solution]

Hi,

This happens usually due to a system being
mounted (/dev/root) in single-user mode
or LVM mainetenance mode. TO fix it do this:

# rm /etc/mnttab
# mount -a

Check to make sure that /dev/vg00/lvol3 is
set to be mounted on /

HTH
Michael

[S.K. Chan]

To find out which PV (or disk) in your vg00 do this ..
# vgdisplay -v vg00 | more

[Tommy_6]

Fay,

This is usually caused by when the system is booted into maintence mode. You can fix this by mounting / back to lvol3. All you need to do is:

# rm /etc/mnttab
# mount -a.

You might want to make a back up of mnttab first. This should solve your problem.

Tommy