Filesystem not mounting after machine reboot

[kaushikbr]

Hi

I have created a new volume group & added 3 LVs in the vg. I have configured them to mount at every reboot. However when I reboot the machine the filesystems are not mounting automatically. I see the following error messages in the /etc/rc.log

Mount file systems
Output from "/sbin/rc1.d/S100localmount start":
----------------------------
mountall: cannot mount /dev/vg01/home
mountall: diagnostics from mount
vxfs mount: Cannot open /dev/vg01/home: No such device or address
mountall: cannot mount /dev/vg01/bptmlogs
mountall: diagnostics from mount
vxfs mount: Cannot open /dev/vg01/bptmlogs: No such device or address
mountall: cannot mount /dev/vg01/appmgmt
mountall: diagnostics from mount
vxfs mount: Cannot open /dev/vg01/appmgmt: No such device or address
checking quotas

But after the machine reboots, if I change the vg availability by running "vgchange -a y vg01" and try mounting them again using mountall, the y can be mounted. I do not understand what is the problem.

/etc/fstab

/dev/vg01/home /home vxfs rw,suid,largefiles,delaylog,datainlog 0 2
/dev/vg01/appmgmt /appmgmt vxfs rw,suid,largefiles,delaylog,datainlog 0 2
/dev/vg01/bptmlogs /bptm_logs vxfs rw,suid,largefiles,delaylog,datainlog 0 2


thanks in advance for all you suggestions.

Regards
Kaushik

[Victor BERRIDGE]

Have a look in your /etc/lvmrc

All the best
Victor

[Duncan Edmonstone · Accepted solution]

Is the machine part of a Serviceguard Cluster?

If so, take a look at /etc/lvmrc. If AUTO_VG_ACTIVATE=0 then you will need to add an entry for vg01 to the custom_vg_activation() function.

ALternative possibility - is theis system running some rather old Secure Path software?

HTH

Duncan

[kaushikbr]

Hi Duncan,

Yes this machine is a part of the Service Guard cluster, and the AUTO_VG_ACTIVATE is set to 1. However I do not have anything for vg01 in the custom_vg_activation function. I will include vg01 in this function.

Thanks & Regards
Kaushik

[Patrick Wallek]

What does 'ls -l /dev/vg01' show? You should see all of your LVs listed. Are you sure you got your LV names correct?

Also try doing a 'vgdisplay -v vg01' and see what it shows your LV names to be. Make sure your LV names from the vgdisplay output match what you have in /etc/fstab.

[kaushikbr]

Hi Duncan

I just realised, I need to set AUTO_VG_ACTIVATE=1 or have some customized commands like vgchange in the custom_vg_activation. Now since the VG_ACTIVATE=1, I need not modify the custom_vg_activation function. Please correct me if I'm wrong.

Thanks and Regards
Kaushik

[Duncan Edmonstone]

Kaushik,

If this *is* a Serviceguard cluster node, then AUTO_VG_ACTIVATE *should* be set to 0, otherwise when this node boots it will attempt to activate all VGs, including those for Serviceguard packages that are running on other nodes.

The correct way to configure this file on a Serviceguard node is to have AUTO_VG_ACTIVATE=0 and then have entries in custom_vg_activation () for the non-Serviceguard VGs.

So lets say I have a host with 4 VGs. vg00 and vg01 are local non-Serviceguard VGs and vg02 and vg03 are Serviceguard VGs. Here's what the relevant parts of /etc/lvmrc might look like:

AUTO_VG_ACTIVATE=0

...

custom_vg_activation()
{
/sbin/vgchange -a y -s vg00
/sbin/vgchange -a y -s vg01
parallel_vg_sync /dev/vg00 /dev/vg01
return 0
}


HTH

Duncan

[kaushikbr]

Sorry Duncan

My mistake, I was looking on the wrong machine.
We have 2 similar clusters, I was looking on the cluster where the AUTO_VG_ACTIVATE is set 1, and the filesystems mount ok on this cluster, however the cluster with the problem AUTO_VG_ACTIVATE is set to 0.

Thanks for your valuable suggestion.
Regards
Kaushik

[Patrick Wallek]

You are correct.

If AUTO_VG_ACTIVATE is 0 (ZERO) then you need to have command in the custom_vg_activation section. If AUTO_VG_ACTIVATE is a non-zero value, then all VG's should be activated automatically.

[Duncan Edmonstone]

See my note above.

AUTO_VG_ACTIVATE should *never* be set to 1 on a Serviceguard cluster. You need to fix that.

HTH

Duncan

[kaushikbr]

Hi Duncan

I have learnt a valuable lesson.
I will do as you have suggested.
Set AUTO_VG_ACTIVATE to 0, and update the custom_vg_activate function.

Thanks and regards
Kaushik