Ok, next time I'll take a better look at my logs.... I rebooted the node in question while watching logs of another. problem node booted and logs reflected that gfs wasn't letting it join cuz it was expired (seems this cluster has other problems). I rebooted all nodes and all nodes joined the cluster. So, after examining my fencing config, it appears that my problem node does not have it's fence device configured properly. I can see the filesystem from all nodes and things look OK. I will definitely be doing a "gfs_fsck" against the fs though just in case ,filesystems unmounted of course :) Once more lesson in getting clear details when trying to fix problems induced by others Cheers Corey -----Original Message----- From: David Teigland [mailto:teigland@xxxxxxxxxx] Sent: Tuesday, June 13, 2006 10:18 AM To: Kovacs, Corey J. Cc: linux-cluster@xxxxxxxxxx Subject: Re: Someone FSCK'd my GFS filesystem.... On Tue, Jun 13, 2006 at 09:00:46AM -0400, Kovacs, Corey J. wrote: > Ok, this is a doozie, someone used a standard fsck against my GFS > filesystem from a single node. > I can, for some reason still access the filesystem from other nodes > and things look ok. I've never had this happen to my systems before > and quite frankly am at a loss as to what my options are. The node > from which the fsck was run, hangs when tryng to mount the filesystem > so I believe it's a problem with the journals. Is there a way to > recover from this other then completely rebuilding the filesystem? I would unmount all the nodes and have one run gfs_fsck. Dave -- Linux-cluster@xxxxxxxxxx https://www.redhat.com/mailman/listinfo/linux-cluster
