i dont start vg01 automatic

[Flavio Lacks]

Hi folks,

i write /dev/vg01 in fstab, but dont up vg01, i need start in command line, where i write this for initializing in rebooting ?

tanks for all

[Devender Khatana · Accepted solution]

Hi,

Your question is not clear. What do you want ?

Activate vg01 automatically when rebooting.
Or
Not activating vg01 when rebooting.

Set AUTO_VG_ACTIVATE=0 in /etc/lvmrc file if you do not want all other VG's then vg00 to be activated at boot time.

The changes written to /etc/fstab made by you are not correct. It should include file systems to be mounted automatically from activated VGs and can not effect activation of the VG.

HTH,
Devender

[Hakan Aribas]

you can mount file systems automatically during bootup by placing information about your file system in the /etc/fstab file. You cannot up volume groups via this way.

[Flavio Lacks]

i want automatically mount vg01, i write 4 command line in fstab
vgchange -a y /dev/vg01
vgchange -n /dev/vg01
mount /dev/vg01/export /exportacao
mount /dev/vg01/backup /exportacao

but while rebooting don´t up vg01, i need write in prompt for up

[Raj D.]

Hi Flavio ,

no need to write vgname but to lvol name in /etc/fstab , which in turn will mount the filesystem , belongs to that lvol:

Here is a typical /etc/fstab entry should be :

/dev/vg00/lvol22 /home/fs1 vxfs log,nodatainlog,nolargefiles,rw,suid 0 2
/dev/vg00/lvol23 /opt/fs2 vxfs log,nodatainlog,nolargefiles,rw,suid 0 2


Cheers,
Raj.

[Flavio Lacks]

exist mc service guard, but 2 machines and 2 different systems, while i no resolve this problem i need up vg01 automatically

[Steven E. Protter]

SG requires you to disable auto startup of all volume groups that may be activated by more than one node of your cluster.

http://forums1.itrc.hp.com/service/forums/questionanswer.do?threadId=799306

AUTO_VG_ACTIVATE=1

That will set a volume group to auto activate on boot. You need VG00 to work this way.

If a Volume group will be activated by more than one node, you MUST set the parameter to 0. To not do so and to activate a cluster that activates VG01 in your case will lead to a catastrophic system failure.

The
custom_vg_activation

Will insure that when your cluster starts the primary node will activate vg01 and the secondary will not but be able to when a package requires it.

SEP

[Devender Khatana]

Hi,

If the nodes are part of cluster you should not set AUTO_VG_ACTIVATE=1.

Also if you want a VG to be activated by itself on reboot then add an entry in /etc/lvmrc file liks this
===============================
ustom_vg_activation()
{
/sbin/vgchange -a y /dev/vg01
# parallel_vg_sync "/dev/vg00 /dev/vg01"
# parallel_vg_sync "/dev/vg02 /dev/vg03"

return 0
}
================================

Apart from this also put entries in proper syntax in /etc/fstab for the file systems belonging to this VG to be mounted automatically.


The entries put in /etc/fstab earlier are not proper. These should be added to achive this.

/dev/vg01/export /exportacao vxfs delaylog 0 2

/dev/vg01/backup /exportacaob vxfs delaylog 0 2

Also you added two entries to mount on the same point which is not correct.

HTH,
Devender

[Flavio Lacks]

this command /sbin/vgchange -a y /dev/vg01 Can i write this command in the fstab ?
after mount the vg ?

[Steven E. Protter]

No.

/etc/fstab is the filesystem table, hence the naming.

Volume groups are activated prior to the automatic mount of filesystems listed in /etc/fstab

Note that /etc/fstab usually contains references the the volume groups, these get activated first.

lvmrc for volume groups
fstab for filesystems

SEP

[Mel Burslan]

Flavio,

A standalone system and a serviceguard system are two different things when it comes to vg activation. I understand that English is not your strong point but if I am understnading you correctly, you have two system running in a serviceguard cluster and these systems are running different packages when the cluster comes up. Is this right ? If it is right, leave the /etc/lvmrc and /etc/fstab alone. DO NOT TOUCH THEM !.

On systems running serviceguard, all you need to autoactivate at the boot time is vg00 and it is activated regardless of if you want it or not.

The rest is upto the cluster and package startup.

But if the vg01 is not a part of any cluster package, you still can not set

AUTO_VG_ACTIVATE=1

instead, you will find the custom vg activation function in the /etc/lvmrc and will modify it as follows (after the comment lines insert this one line)

/sbin/vgchange -a y /dev/vg01

then you will need to add these two lines to your /etc/fstab (these are according to what you said previously)


/dev/vg01/export /exportacao vxfs delaylog,rw,suid 0 2
/dev/vg01/backup /exportacaob vxfs delaylog,rw,suid 0 2

at this moment you should be good to go.

[Flavio Lacks]

if i write AUTO_VG_ACTIVATE=1 in lvmrc, my packages don´t up,

[Mel Burslan]

you still need to set AUTO_VG_ACTIVATE=0 then modify the custom_vg_activation() section as described in the posts above.