(sorry about topposting.) Just changing the timeout would only mask the problem. The real issue is that running 'df' on either node causes a hang. All other operations seem fine, files can be created and deleted as normal with the results showing up on both. I'd like to work out why it's hanging on df so I can fix it and get my monitoring and cron scripts running again :) -- joe. -----Original Message----- From: gluster-users-bounces at gluster.org [mailto:gluster-users-bounces at gluster.org] On Behalf Of Daniel Maher Sent: 17 January 2011 12:48 To: gluster-users at gluster.org Subject: Re: df causes hang On 01/17/2011 10:47 AM, Joe Warren-Meeks wrote: > Hey chaps, > > Anyone got any pointers as to what this might be? This is still causing > a lot of problems for us whenever we attempt to do df. > > -- joe. > > -----Original Message----- > However, for some reason, they've got into a bit of a state such that > typing 'df -k' causes both to hang, resulting in a loss of service for42 > seconds. I see the following messages in the log files: > > 42 seconds is the default tcp timeout time for any given node - you could try tuning that down and seeing how it works for you. http://www.gluster.com/community/documentation/index.php/Gluster_3.1:_Se tting_Volume_Options -- Daniel Maher <dma+gluster AT witbe DOT net> _______________________________________________ Gluster-users mailing list Gluster-users at gluster.org http://gluster.org/cgi-bin/mailman/listinfo/gluster-users
