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

List:       gfs-bugs
Subject:    [gfs-bugs] [Bug 174] New - restart of memexpd causes panic in clients
From:       bugzilla-daemon () bender ! sistina ! com
Date:       2001-01-25 13:48:57
[Download RAW message or body]

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

*** shadow/174	Thu Jan 25 07:48:57 2001
--- shadow/174.tmp.10545	Thu Jan 25 07:48:57 2001
***************
*** 0 ****
--- 1,38 ----
+ Bug#: 174
+ Product: GFS
+ Version: Public CVS
+ Platform: 
+ OS/Version: All
+ Status: NEW   
+ Resolution: 
+ Severity: blocker
+ Priority: P4
+ Component: memexpd
+ AssignedTo: gfs-bugs@sistina.com                            
+ ReportedBy: terje.eggestad@scali.no               
+ URL: 
+ Summary: restart of memexpd causes panic in clients
+ 
+ I use a stock 2.2.18 kernel and GFS update'ed to tag  v4_0_zarniwoop, 
+ which I belive is the released prod version.
+ 
+ I have two servers providing network block devices (one pool), and one of these
+ run the memexpd. And now two clients.
+ 
+ Now, if i kill and restart the memexpd daemon the two clients panic, and I've
+ recorded two different errors (not on the same occation! the first time I
+ encountered this problem was on a reboot of the node with the memexpd):
+ 
+ memexp: Assertion failed on line 698 of file ../client_state.c
+ memexp: assertion: "rdf.inuse"
+ memexp: time = ...
+ cidbuf 1 buffer not inuse
+ kernel Panic:
+ memexp: The End
+ 
+ memexp: Assertion failed on line 552 of file ../mount_state.c
+ memexp: assertion: "0"
+ memexp: time = ...
+ Invalid mount lock owner (0)
+ kernel Panic:
+ memexp: The End
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]