[prev in list] [next in list] [prev in thread] [next in thread] 

List:       gfs-bugs
Subject:    [gfs-bugs] [Bug 226] Changed - nodes hang after reading journal
From:       bugzilla-daemon () sistina ! com
Date:       2001-03-20 15:47:58
[Download RAW message or body]

http://bugzilla.sistina.com/show_bug.cgi?id=226

*** shadow/226	Mon Mar 19 18:14:21 2001
--- shadow/226.tmp.11448	Tue Mar 20 09:47:58 2001
***************
*** 248,250 ****
--- 248,266 ----
  node: 131.225.7.51  1   SM:  meatware
  node: 131.225.7.66  2   SM:  meatware
  node: 131.225.7.67  3   SM:  meatware
+ 
+ ------- Additional Comments From annis@fnal.gov  2001-03-20 09:47 -------
+ Following David Teigland's suggestions,
+ I made sure to restart the memexpd before bringing up the first GFS node.
+ This seems to have worked. Thanks!
+ 
+ I thought I had tried that, but what I probably did was to get a machine into a
+ hung state, then restart the memexpd, then reboot. I believe that failed to
+ work.
+ 
+ I'm still unclear what happened exactly, and wouldn't mind an explanation, but
+ most important to me, my cluster is back up.
+ 
+ thanks again,
+ Jim 
+ 
Read the GFS HOWTO http://www.sistina.com/gfs/Pages/howto.html
gfs-bugs mailing list
gfs-bugs@sistina.com
http://lists.sistina.com/mailman/listinfo/gfs-bugs
Read the GFS Howto:  http://www.sistina.com/gfs/Pages/howto.html

[prev in list] [next in list] [prev in thread] [next in thread] 

Configure | About | News | Add a list | Sponsored by KoreLogic