On Thu, 20 Dec 2007, Jonathan Biggar wrote:
James Chamberlain wrote:
Hi all,
I've got a three node CentOS 5 x86-64 CS/GFS cluster running kernel
2.6.18-53.el5. Last night, I tried to grow two of the file systems on it.
I ran lvextend and then gfs_grow on node3, with node2 serving the file
systems out to the local network. While gfs_grow was running, node2
failed the service and I couldn't get it to restart. It looked to me like
neither node1 nor node2 was aware of the lvextend I had run on node3. I
had to reboot the full cluster to bring everything back online.
If you ran lvextend on node3 while node2 had the filesystem mounted and
exported via NFS, then you did the wrong thing. CLVM lets the nodes share
information about the PVs, VGs and LVs, but not information about the
contents of an LV.
You needed to run lvextend on the node that had the filesystem mounted.
All three nodes had the (GFS) filesystem mounted. I'll note that exactly
this operation this worked for me a couple of weeks ago on a CentOS 4
CS/GFS cluster.
Thanks,
James
--
Linux-cluster mailing list
Linux-cluster@xxxxxxxxxx
https://www.redhat.com/mailman/listinfo/linux-cluster
