I wasnt able to mount gfs2 after upgrading to Centos 5.3. I have this error:

/sbin/mount.gfs2: invalid device path "/dev/VolGrp01/LogVol00
/sbin/mount.gfs2: invalid device path "/dev/VolGrp01/LogVol01
/sbin/mount.gfs2: invalid device path "/dev/VolGrp01/LogVol02

This worked fine using Centos 5.2

Message is invalid path not invalid filesystem.

Type "ls -l /dev/VolGrp01/LogVol0?" to see if any of the paths exists.

You don't indicate from what OS/version you did the upgrade to CentOS 5.3.

The names are for Logical Volumes (LVs) from Logical Volume Manager (LVM).

Typically these days the path used for mounting these on Fedora/RHEL/CentOS are in the form of:
/dev/mapper/VolGroup00-LogVol00
/dev/mapper/VolGroup00-LogVol01
/dev/mapper/VolGroup00-LogVol02

(or maybe /dev/mapper/VolGrp01/LogVol0... in your case.)

You may want to see if those exists and try mounting using the /dev/mapper names instead.

Here's the complete scenario.

I have problem mounting the gfs2 after I upgraded to 5.3. Previously it was working on version 5.2. Im using conga to administer the cluster.

When I do fdisk, I can see the block device using the iscsi.

[root@head01 ~]# fdisk -l

Disk /dev/sda: 160.0 GB, 160041885696 bytes
255 heads, 63 sectors/track, 19457 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes

Device Boot Start End Blocks Id System
/dev/sda1 * 1 13 104391 83 Linux
/dev/sda2 14 19457 156183930 8e Linux LVM

Disk /dev/sdb: 250.0 GB, 250059350016 bytes
255 heads, 63 sectors/track, 30401 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes

Device Boot Start End Blocks Id System
/dev/sdb1 * 1 30401 244196001 8e Linux LVM

Disk /dev/sdc: 250.0 GB, 250059350016 bytes
255 heads, 63 sectors/track, 30401 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes

Device Boot Start End Blocks Id System
/dev/sdc1 * 1 30401 244196001 8e Linux LVM
[root@head01 ~]#


Cluster configuration is working fine and all nodes are on the cluster

<?xml version="1.0"?>
<clustat version="4.1.1">
<cluster name="MAJOR" id="10768" generation="308444"/>
<quorum quorate="1" groupmember="0"/>
<nodes>
<node name="head01.mydomain.com" state="1" local="0" estranged="0" rgmanager="0" rgmanager_master="0" qdisk="0" nodeid="0x00000001"/>
<node name="head02.mydomain.com" state="1" local="1" estranged="0" rgmanager="0" rgmanager_master="0" qdisk="0" nodeid="0x00000002"/>
<node name="head03.mydomain.com" state="1" local="0" estranged="0" rgmanager="0" rgmanager_master="0" qdisk="0" nodeid="0x00000003"/>
</nodes>
</clustat>

Cluster Status for MAJOR @ Wed Apr 15 10:51:37 2009
Member Status: Quorate

Member Name ID Status
------ ---- ---- ------
head02.mydomain.com 1 Online
head01.mydomain.com 2 Online, Local
head03.mydomain.com 3 Online

[root@head01 ~]#


If I do a manual mounting, here's the error:

[root@head01 ~]# mount -a
/sbin/mount.gfs2: invalid device path "/dev/VolGroup01/LogicalVol00"
/sbin/mount.gfs2: invalid device path "/dev/VolGroup01/LogicalVol02"
/sbin/mount.gfs2: invalid device path "/dev/VolGroup01/LogicalVol01"


Here's the fstab generated using conga when I was still using 5.2

/dev/VolGroup00/LogVol00 / ext3 defaults 1 1
LABEL=/boot /boot ext3 defaults 1 2
devpts /dev/pts devpts gid=5,mode=620 0 0
tmpfs /dev/shm tmpfs defaults 0 0
proc /proc proc defaults 0 0
sysfs /sys sysfs defaults 0 0
/dev/VolGroup00/LogVol01 swap swap defaults 0 0
/dev/VolGroup01/LogicalVol00 /shared01 gfs2 defaults 0 0
/usr/local/swapfile swap swap defaults 0 0
/dev/VolGroup01/LogicalVol02 /shared03 gfs2 defaults 0 0
/dev/VolGroup01/LogicalVol01 /shared02 gfs2 defaults 1 2

Do I need a fresh 5.3 re-installation? I tried rebooting the old kernel but no luck. I noticed that the following were removed on 5.3

# kmod-gfs2-1.92
# kmod-gfs2-PAE-1.92
# kmod-gfs2-xen-1.92

Is this the cause why I cant mount the that was used to be mounted? Anybody can help me please.. TIA

I'm assuming you were typing that up while I was typing my previous post since nothing in what you wrote mentions anything I wrote. Look above your last post to see what I wrote.