PKG halting failed

[kunjuttan]

Hi All,

         I am facing one problem in halting one package in my 2node cluster.I am having 4 vg in cluster pkg.Cluster was up and running smoothly till some days back.I added one new LV In the 4th VG.And I didnt make it as shared LV,instead as a local FS.Now this is creating problem when I am trying to bring this package.It is saying like VG2 cant be deactivated.Now what is the solution for this.Can I add the newly created FS into cluster.If yes,whts the procedure.If no,what is the other solution.

OS - HP-UX 11.31

MCSG - A.11.20.00.01

[Turgay Cavdar]

Hi ,

> And I didnt make it as shared LV,instead as a local FS.

It is not very clear what you mean here, can you write all steps you did on your lv adding operation. And also send the log file entries.

[Stephen Doud]

It would be helpful if you provided actual failure messages!

Usually a VG cannot be deactivated when files are still open on the VG volumes (file systems). Use fuser on each logical volume/mount point, or lsof (non_HP utility) to identify processes that intiated the I/O, then learn why they have not completed the I/O.

[Srinivasan Palani · Accepted solution]

Hi Kunjuttan,

I think it is better to check if some users or processes still using that particular VG that can't be deactivated, as turgay and stephen has mentioned.

Did you add a lvol to the same VG that can't be deactivated (VG2) ?

As far as I know it would not cause issues during the package halt even if you did not reimport the VG in the other node(s) after adding the logical volume to it in one node but It will certainly cause issues while starting the package in the other node(s). If that is what you are facing now. Then, you need to reimport the VG (in other nodes) to which you have added the logical volume, the steps are as follows.

Steps for the node that has the VG active:

1)create a mapfile
vgexport -v -p -s -m /tmp/<vg name>.map <vg name>

2)copy the map file to the other node


Steps to be performed on each other node(s):

3. Note VG minor number and permissions/ownership:
node2# ll /dev/<vg name>
total 12
crw-r----- 1 root sys 64 0x010000  group
brw-r----- 1 root sys 64 0x010001  lvol2
crw-r----- 1 root sys 64 0x010001  rlvol2

4. Export the VG:
node2# vgexport <vg name>

5. Re-create VG directory:
node2# mkdir /dev/<vgname>

6. Re-create VG group special file, use minor number noted above.
node2# mknod /dev/<vgname>/group c 64 0x010000

7. Run vgimport using the copied mapfile:
node2# vgimport –v –s –m /tmp/<vgname>.map <vgname>

8. Change permissions and ownership of the VG directory and its device special files
according to the information noted above.

9. Test the activation of the VG in read-only mode and perform vgcfgbackup:
node2# vgchange –a r <vgname>
node2# vgcfgbackup <vgname>

Regards,

Srinivasan Palani