VG issue at the time of package start

[Fenny_1]

Hi All,
I'm facing a very strange issue. Am trying for start the package but its failing by giving the following error.

########### Node "tppora51": Starting package at Sat Jul 7 15:33:17 PST 2007 ###########
Jul 7 15:33:17 - Node "tppora51": Activating volume group vgtdevapp with exclusive option.
Activated volume group in Exclusive Mode.
Volume group "vgtdevapp" has been successfully changed.
Jul 7 15:33:17 - Node "tppora51": Activating volume group vgtdevdata with exclusive option.
Activated volume group in Exclusive Mode.
Volume group "vgtdevdata" has been successfully changed.
Jul 7 15:33:17 - Node "tppora51": Checking filesystems:
/dev/vgtdevapp/lvol1
/dev/vgtdevdata/lvol1
/dev/vgtdevdata/lvol3
/dev/vgtdevapp/rlvol1:file system is clean - log replay is not required
/dev/vgtdevdata/rlvol1:file system is clean - log replay is not required
fsck: /etc/default/fs is used for determining the file system type
file system is clean - log replay is not required
Jul 7 15:33:18 - Node "tppora51": Mounting /dev/vgtdevapp/lvol1 at /u22/app/oracle
Jul 7 15:33:19 - Node "tppora51": Mounting /dev/vgtdevdata/lvol1 at /db22/oradata/TIBCODEV/archive
Jul 7 15:33:19 - Node "tppora51": Mounting /dev/vgtdevdata/lvol3 at
mount: /dev/vgtdevdata/lvol3 was either ignored or not found in /etc/fstab
ERROR: Function check_and_mount
ERROR: Failed to mount /dev/vgtdevdata/lvol3
Jul 7 15:33:19 - Node "tppora51": Unmounting filesystem on /dev/vgtdevdata/lvol1
Jul 7 15:33:19 - Node "tppora51": Unmounting filesystem on /dev/vgtdevapp/lvol1
Jul 7 15:33:20 - Node "tppora51": Deactivating volume group vgtdevapp
Deactivated volume group in Exclusive Mode.
Volume group "vgtdevapp" has been successfully changed.
Jul 7 15:33:20 - Node "tppora51": Deactivating volume group vgtdevdata
Deactivated volume group in Exclusive Mode.
Volume group "vgtdevdata" has been successfully changed.

########### Node "tppora51": Package start failed at Sat Jul 7 15:33:20 PST 2007 ###########


I checked it by manually mounting the lvol on the directory and its mounting properly but it's not able to mount with the package control script.

Can anyone help me in this regard. your urgent reponse will be highly appreciated.

[Matti_Kurkela]

Note that the general form of SG's filesystem mount messages is "Mounting at " but with /dev/vgtdevdata/lvol3 the part seems to be a null string.

This makes the "mount" command look into /etc/fstab, which normally *does not* have any mention of ServiceGuard package filesystems. So the mount command fails, because nothing tells it where it should mount /dev/vgtdevdata/lvol3 to.

Check the filesystem definitions in your package control scripts very carefully: it is very likely that there is a typo in there.

MK

[Fat Scrape · Accepted solution]

Hi Fenny,

if
1) /dev/vgtdevapp/lvol1 is mounted at /u22/app/oracle
2) /dev/vgtdevdata/lvol1 is mounted at /db22/oradata/TIBCODEV/archive
3) where is /dev/vgtdevdata/lvol3 mounted? I think that /dev/vgtdevdata/lvol3 is trying to mount at "" null moint point

"Mounting /dev/vgtdevdata/lvol3 at
mount: /dev/vgtdevdata/lvol3 was either ignored or not found in /etc/fstab"

Please Could you verify if Filesystem section in the control file present in your package directory is correct:

LV[0]=/dev/vgtdevapp/lvol1
FS[0]=/u22/app/oracle
FS_MOUNT_OPT[0]=""
LV[1]=/dev/vgtdevdata/lvol1
FS[1]=/db22/oradata/TIBCODEV/archive
FS_MOUNT_OPT[1]=""
LV[2]=/dev/vgtdevdata/lvol3
FS[2]= # which is the mount point set, is correct?
FS_MOUNT_OPT[2]=""

Regards,

Fat

[skt_skt]

The first suspect would be FS entry in cntl files..

next you can try is cmcheckconf/cmapplyconf on that package to make sure everything is Ok.

[Doug O'Leary]

Hey;

Others have mentioned the probable issue in that the FS array and LV array aren't completely in sync.

It's this exact reason why I always develop a package fstab file for the mount points then add logic to the control file to read the fstab instead of using those arrays.

The big advantage to this approach is that most admins with more than a day or two experience are already familiar with the fstab file and how to update it.

The only disadvantage is that it's not completely standard and you'll have to ensure other admins that support the cluster are familiar with the approach.

Here's a package fstab file that's used for a SAP environment:

#############################################################################
# sapABC package fstab file
#############################################################################
/dev/vgsapABC/oracle_ABC /oracle/ABC vxfs delaylog,largefiles 0 2
/dev/vgsapABC/arch /oracle/ABC/saparch1 vxfs delaylog,largefiles 0 2
/dev/vgsapABC/saparch1 /oracle/ABC/saparch vxfs delaylog,largefiles 0 2
/dev/vgsapABC/reorg /oracle/ABC/sapreorg vxfs delaylog,largefiles 0 2
/dev/vgsapABC/ora920_64 /oracle/ABC/920_64 vxfs delaylog,largefiles 0 2
/dev/vgsapABC/archive /export/usr/sap/ABC/archive vxfs delaylog,largefiles 0 2
/dev/vgsapABC/usrsapABC /usr/sap/ABC/DVEBMGS09 vxfs delaylog,largefiles 0 2
/dev/vgsapABC/put /usr/sap/put vxfs delaylog,largefiles 0 2
/dev/vgsapABC/sapmnt /export/sapmnt/ABC vxfs delaylog,largefiles 0 2
/dev/vgsapABC/stage /oracle/stage vxfs delaylog,largefiles 0 2
/dev/vgsapABC/trans /export/usr/sap/trans vxfs delaylog,largefiles 0 2


And, here's the logic for reading it in the control file:

Fstab=/etc/cmcluster/E1P/fstab_E1P
set -A LV
set -A FS
set -A FS_TYPE
set -A FS_MOUNT_OPT
set -A FS_UMOUNT_OPT
set -A FS_FSCK_OPT
x=0
egrep -v "^$|^#" ${Fstab} | while read lv mp type opts a b
do
LV[${x}]=${lv}
FS[${x}]=${mp}
FS_TYPE[${x}]=${type}
FS_MOUNT_OPT[${x}]="-o ${opts}"
FS_UMOUNT_OPT[${x}]=""
FS_FSCK_OPT[${x}]=""
x=$((x+1))
done

HTH;

Doug

[Fenny_1]

Problem is resolved. Thanks for everyone help