I am upgrading a system with a GFS 6.0 filesystem from RHEL 3 to CentOS 5, and subsequently GFS 6.0 to 6.1. I've followed the instructions here: http://www.redhat.com/docs/manuals/csgfs/browse/rh-gfs-en/ap-license.html and subsequently ran gfs_tool sb device proto lock_dlm on my gfs lv The cluster is up and quorate, and clvmd sees the gfs lv, but when I try to mount it, I get: # mount -t gfs -o upgrade /dev/mapper/pool_gfs-pool_gfs /VAULT10/ /sbin/mount.gfs: there appears to be a GFS2, not GFS, filesystem on /dev/mapper/pool_gfs-pool_gfs I'm not sure why this is failing. For grins, I tried mounting it as a gfs2 filesystem and this is what I get: # mount -t gfs2 -o upgrade /dev/mapper/pool_gfs-pool_gfs /VAULT10/ /sbin/mount.gfs2: there appears to be a GFS, not GFS2, filesystem on /dev/mapper/pool_gfs-pool_gfs I have successfully performed the upgrade if I use centos 4 as an intermediate step in the upgrade and perform the upgrade steps there and the conversion from lock_gulmd to dlm. However, there are several clusters we need to do this with, so that's a painful option to avoid if possible. Here is the output from gfs_tool: # gfs_tool sb /dev/mapper/pool_gfs-pool_gfs all mh_magic = 0x01161970 mh_type = 1 mh_generation = 0 mh_format = 100 mh_incarn = 0 sb_fs_format = 1308 sb_multihost_format = 1401 sb_flags = 0 sb_bsize = 4096 sb_bsize_shift = 12 sb_seg_size = 16 no_formal_ino = 21 no_addr = 21 no_formal_ino = 22 no_addr = 22 no_formal_ino = 25 no_addr = 25 sb_lockproto = lock_dlm sb_locktable = cma:pool_gfs no_formal_ino = 23 no_addr = 23 no_formal_ino = 24 no_addr = 24 sb_reserved = 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 thanks, -chris -- Linux-cluster mailing list Linux-cluster@xxxxxxxxxx https://www.redhat.com/mailman/listinfo/linux-cluster
