I wasn't sure which list to, so I chose both cluster and lvm.
My current configuration:
2 Node RHEL 5.2 cluster with multiple GFS on top of logical volumes in one volume group.
# rpm -q cman lvm2 lvm2-cluster kmod-gfs
cman-2.0.84-2.el5
lvm2-2.02.32-4.el5
lvm2-cluster-2.02.32-4.el5
kmod-gfs-0.1.23-5.el5
I need to move a PV out of this volume group so I attempted to run pvmove /dev/sdk1 but errors about locking on the other node. I assumed this was because of the multiple GFS file systems being used on both nodes (services were spread across the nodes). So I relocated all services to one node and even stopped rgmanager, gfs, clvmd and cman on the idle node to make sure that no locks would remain open.
I still had issues with running the pvmove. I saw these messages:
Sep 24 17:56:48 nodea kernel: device-mapper: mirror log: Module for logging t
ype "clustered-core" not found.
Sep 24 17:56:48 nodea kernel: device-mapper: table: 253:31: mirror: Error cre
ating mirror dirty log
Sep 24 17:56:48 nodea kernel: device-mapper: ioctl: error adding target to ta
ble
And after about 14% of the move was completed, there was another locking message and many processes went into an uninteruptable sleep state. Load on the server shot up to around 80.
I finally had to reboot the node and run pvmove --abort to get everything back to working condition.
Is it not possible to run pvmove on a clustered VG? Any help would be appreciated.
-Jeremy
My current configuration:
2 Node RHEL 5.2 cluster with multiple GFS on top of logical volumes in one volume group.
# rpm -q cman lvm2 lvm2-cluster kmod-gfs
cman-2.0.84-2.el5
lvm2-2.02.32-4.el5
lvm2-cluster-2.02.32-4.el5
kmod-gfs-0.1.23-5.el5
I need to move a PV out of this volume group so I attempted to run pvmove /dev/sdk1 but errors about locking on the other node. I assumed this was because of the multiple GFS file systems being used on both nodes (services were spread across the nodes). So I relocated all services to one node and even stopped rgmanager, gfs, clvmd and cman on the idle node to make sure that no locks would remain open.
I still had issues with running the pvmove. I saw these messages:
Sep 24 17:56:48 nodea kernel: device-mapper: mirror log: Module for logging t
ype "clustered-core" not found.
Sep 24 17:56:48 nodea kernel: device-mapper: table: 253:31: mirror: Error cre
ating mirror dirty log
Sep 24 17:56:48 nodea kernel: device-mapper: ioctl: error adding target to ta
ble
And after about 14% of the move was completed, there was another locking message and many processes went into an uninteruptable sleep state. Load on the server shot up to around 80.
I finally had to reboot the node and run pvmove --abort to get everything back to working condition.
Is it not possible to run pvmove on a clustered VG? Any help would be appreciated.
-Jeremy
-- Linux-cluster mailing list Linux-cluster@xxxxxxxxxx https://www.redhat.com/mailman/listinfo/linux-cluster
