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

List:       gfs-bugs
Subject:    [Bug 53] Changed - gfs takes too long to umount.
From:       gfs-bugzilla-daemon () borg ! umn ! edu
Date:       2000-02-25 7:40:11
[Download RAW message or body]

http://www.globalfilesystem.org/bugzilla/show_bug.cgi?id=53

*** shadow/53	Thu Feb 24 12:43:40 2000
--- shadow/53.tmp.78906	Fri Feb 25 01:40:11 2000
***************
*** 15,17 ****
--- 15,28 ----
  
  sometimes if gfs is really taking its time umounting, it will expire on the
  server before it can finish.
+ 
+ ------- Additional Comments From kpreslan@sistina.com  2000-02-25 01:40 -------
+ This shouldn't be GFS.  All the stuff that GFS does that takes a long time to do
+ happens before we unmount the lock module.  The lock module should still be
+ heartbeating during this time. (In fact, the lock module doesn't even know that
+ an unmount is happening.)
+ 
+ And anyway, by the time the lock module unmount() lock is called, there
+ shouldn't be any held locks, so why is it expiring?
+ 
+ 

-
To unsubscribe from this list: send the line "unsubscribe gfs-bugs" in
the body of a message to majordomo@borg.umn.edu
Read the GFS Howto:  http://www.globalfilesystem.org/howtos/gfs_howto/

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

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