Mounting error

[Jim Dustan]

i did a lvreduce on a LV and now I am getting this error after rebooting...
mount /dev/vg00/lvol4 /tmp
vxfs mount: /dev/vg00/lvol4 is already mounted, /tmp is busy,
or allowable number of mount points exceeded

[Steven E. Protter]

bdf please

It would appear /tmp is already mounted. Thats normal on a running system.

There may be an inconsistency in the /etc/fstab setup

SEP

[Jim Dustan]

BDF

bdf
Filesystem kbytes used avail %used Mounted on
/dev/vg00/lvol3 212992 84416 127624 40% /
/dev/vg00/lvol1 298928 80032 189000 30% /stand
/dev/vg00/lvol8 2621440 406648 2197920 16% /var
/dev/vg00/lvol7 2015232 1112600 895592 55% /usr
/dev/vg00/lvol6 2539520 1614720 917584 64% /opt
/dev/vg00/lvol5 32768 2280 30264 7% /home
#

/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/lvol3 / vxfs delaylog 0 1
/dev/vg00/lvol1 /stand hfs defaults 0 1
/dev/vg00/lvol4 /tmp vxfs delaylog 0 2
/dev/vg00/lvol5 /home vxfs delaylog 0 2
/dev/vg00/lvol6 /opt vxfs delaylog 0 2
/dev/vg00/lvol7 /usr vxfs delaylog 0 2
/dev/vg00/lvol8 /var vxfs delaylog 0 2

[Stf]

You probably have to comment /tmp lines in /etc/fstab...

Stf ;-)

[Jim Dustan]

comment out and then reboot?

when i did the newfs, I received this as well. it sees the correct size but it isn't mounting.

# newfs -F vxfs /dev/vg00/rlvol4
version 4 layout
3080192 sectors, 3080192 blocks of size 1024, log size 1024 blocks
unlimited inodes, largefiles not supported
3080192 data blocks, 3078328 free data blocks
94 allocation units of 32768 blocks, 32768 data blocks

[Tom Danzig]

Did you remove the lvol BEFORE unmounting it or possibly try to mount the same lvol/mountpoint twice? There was a known LVM bug which caused this behavior and a patch issued to fix it. Do a search in the ITRC patch database.

[Jim Dustan]

i was under the impression that i wouldn't have to unmount with HP OnlineJFS?? so, I did the lvreduce without unmounting /tmp and then the newfs...

[Tom Danzig]

Reducing a file system and then an lvol is risky at best. It appears that /tmp is not mounted and showing up in the bdf listing. I would try to boot into single user mode and recreate the file system on the /tmp lvol (/dev/vg00/lvol4 if I'm not mistaken) and see if that helps.

[Tom Danzig]

The patch I was refering to above was PHKL_27212. From the read me below:
( SR:8606236403 CR:JAGae05460 )
Attempting to mount the same filesystem on two
different directories may leave the corresponding
Logical Volume Manager (LVM) volume group in a state in
which it cannot be deactivated, even though its logical
volumes are not in use. The following steps would cause the
problem to be seen:

# mount /dev/vg100/lvol1 /tmp_mnt
# mount /dev/vg100/lvol1 /tmp_mnt2
vxfs mount: /dev/vg100/lvol1 is already mounted, /tmp_mnt2
is busy, or allowable number of mount points exceeded
# umount /tmp_mnt
# vgchange -a n vg100
vgchange: Couldn't deactivate volume group "vg100":
Device busy


This patch has been replaced by patch PHKL_30927