----- "Arend-Jan Wijtzes" <ajwyt...@wise-guys.nl> wrote: > Hi Gluster people, > > We are seeing errors when GlusterFS is being accessed after a long > period (days) of inactivity (the FS is used but not from this > machine).
The error is not related to the inactivity. Take a look at these lines of the log file: > 2009-04-10 16:18:06 E [client-protocol.c:263:call_bail] brick-0-0: > activating bail-out. pending frames = 1. last sent = 2009-04-10 > 16:17:14. last received = 2009-03-30 03:13:43. transport-timeout = 42 > 2009-04-10 16:18:06 C [client-protocol.c:298:call_bail] brick-0-0: > bailing transport A request was sent at 16:17:14 but no reply has been received even at 16:18:06 (= 52 seconds). Since the transport timeout is set to 42 seconds, the request has been aborted. There was probably some kind of network issue which caused the reply to not arrive. Vikas -- Engineer - http://gluster.com/ A: Because it messes up the way people read text. Q: Why is a top-posting such a bad thing? -- _______________________________________________ Gluster-users mailing list Gluster-users@gluster.org http://zresearch.com/cgi-bin/mailman/listinfo/gluster-users
