Disconnection logs were wrongly put in a lower log level during RPC migration. They are fixed in the latest code. On Mon, Jan 17, 2011 at 7:36 PM, Georg H?llrigl <georg.hoellrigl at xidras.com>wrote: > Hello, > > I checked the logfiles one more time. I know why it was impossible to find > the problem. > > When the server rebooted and connects to glusterfs server it logs: > > [2010-08-23 10:15:36] N [client-protocol.c:6246:client_setvolume_cbk] > vgfs-01-001: Connected to 10.0.1.X:7002, attached to remote vol > ume 'community-data-flirty'. > [2010-08-23 10:15:36] N [client-protocol.c:6246:client_setvolume_cbk] > vgfs-01-001: Connected to 10.0.1.X:7002, attached to remote vol > ume 'community-data-flirty'. > > But it doesn't log a message, that there was a problem with one of the > glusterfs-nodes! > > So I would suggest a logging message, when one of the configured hosts > can't be reached. > > > > > Georg > > > Am 15.01.2011 22:24, schrieb Anand Avati: > >> This looks an issue in your setup. One of the clients has very likely not >> connected to both the >> >> servers. You say client volfile are exactly the same. Can you verify if >> DNS (or /etc/hosts entries) >> resolve consistent on all your client nodes? >> >> >> Avati >> >> On 14 January 2011 15:44, Georg H?llrigl <georg.hoellrigl at xidras.com >> <mailto:georg.hoellrigl at xidras.com>> wrote: >> >> Hello, >> >> >> I delete a file on glusterfs but shortly after I have verified that it >> is away, it suddenly >> reappears. >> >> >> I'm using glusterfs 3.0.6. Two servers and several clients with client >> replication. >> >> >> I found out the following things: >> >> - The file only comes back when deleting on one glusterfs client. >> - The deletion works with other clients. >> - The clients have exactly the same configuration and mount options. >> - Remounting or even rebooting the server doesn't solve the problem. >> - The logfiles on the server and the client don't reveal anything about >> the problem. >> - When watching the filesystem on the servers, I see that the file only >> gets deleted on one of >> them. Afterwards it looks like self healing jumps in. >> >> >> Any ideas how to fix this? >> >> >> Regards >> >> Georg >> >> _______________________________________________ >> Gluster-users mailing list >> Gluster-users at gluster.org <mailto:Gluster-users at gluster.org> >> >> http://gluster.org/cgi-bin/mailman/listinfo/gluster-users >> >> >> > _______________________________________________ > Gluster-users mailing list > Gluster-users at gluster.org > http://gluster.org/cgi-bin/mailman/listinfo/gluster-users >
