1 LVM Mounted on 2 mount directories

[Ankit Grover]

Hi,

I am facing a problem regarding mounting of LVOL on a mount point.
There is a VG "vgallahabad" on my HP IA64 box. Its having 2 LVOLs "lvol40" & "lvol41". lvol40 was mounted on /fns/a4 while lvol41 was mounted on /fns/lvp01.
Today the server was re-started and after that I am not able to access 2nd mount dir /fns/lvp01. Its giving errors. Upon checking in SAM, I saw that lvol41 is mounted at 2 points. I am not able to get what is meant by it and how to go about it further.

lvol40 vgallahabad LVM VxFS 20480 0 /fns/lvp01
lvol41 vgallahabad LVM VxFS/VxFS 15360 0 /fns/a4,/fns/lvp01

Regards,
Ankit.

[Peter Godron]

Ankit,
corrupted /etc/lvmtab ??
Try:
vgscan -a -v -p

to check.
If this shows the correct data, please read "man vgscan" to decide, on whether to run command in change mode.

[James R. Ferguson · Accepted solution]

Hi Ankit:

If you rebooted and you still have two directories mounted on the same device, you need to look (first) at '/etc/fstab'. I suspect that your problem lies there. If so, unmount both directories; fix the '/etc/fstab' to reflect the correct mountpoints and devices; and do a 'mount -a'.

To unmount your directories you will need to stop all processes using them. You may find that 'fuser -c /mountpoint' is useful to determine the processes using the mountpoint.

Regards!

...JRF...

[Ankit Grover]

JRF...

I tried out your solution. Fixed everything in all TAB files.
Please check the following error:

[root]/etc#umount /dev/vgallahabad/lvol41
umount: cannot unmount /fns/a4 : Device busy
umount: return error 1.
[root]/etc#fuser -c /dev/vgallahabad/lvol41
/dev/vgallahabad/lvol41: fuser: could not find file system mounted at /dev/vgallahabad/lvol41.

mount -a gives me:
vxfs mount: /dev/vgallahabad/lvol40 is corrupted. needs checking
mount: /dev/vgallahabad/lvol41 is already mounted on /fns/a4

[A. Clay Stephenson]

You are probably going to have to reboot to fix this mess --- and the bad news is that the filesystem may now be hopelessly corrupt. I assume that you have good backups. In any event, make sure that the /etc/fstab entries are all correct and then reboot.

[Ankit Grover]

Thanks experts.
The problem got resolved by running file system check:
fsck -y

Then I made the necessary changes in TAB files and run mount -a.

Cheers,
Ankit