On Tue, Sep 07, 2004 at 07:45:47PM +0100, Brian Marsden wrote: > I have two machines, hestia and hroth1 which are running Red Hat > Enterprise Linux 3.0 AS. The two machines are connected via fibrechannel > to the same storage group on a EMC CX300 array. I have compiled gfs > using the latest src.rpm file that is available and the 2.4.21-15 kernel > patches. All works fine on both nodes for a while (locking is fine, no > corruption, manual fencing works if a machine dies) but then I > experience lockups for processes that access any of the mounted gfs > filesystems. It is hard to reproduce reliably and may occur at any time. > Classic examples are ls /scratch (where /scratch is a gfs filesystem) or > even mount or unmount. Once one process has locked up, no other gfs > filesystems or any commands associated with them work. Only a reboot > will solve the problem - restarting lock_gulm does not help (and has > actually given me a kernel panic on one occasion). When a lockup happens, a few things that might be useful in figuring it out are: A "ps aux" on both nodes and the output of "gfs_tool lockdump /mountpoint" on both nodes. -- Ken Preslan <kpreslan@xxxxxxxxxx>
