Gareth, That bug was fixed long back, i just moved it to fixed state. Gordan, > I have two nodes in AFR mode. If node2 down and I add files to node1, when > the node2 comes up, it cannot see the files. ls doesn't show them. > > However, after I cat/head the files on node1, they appear on node2. > > Is there a way to make this work? I can live with head-ing every file when > a node comes up to force a resync, but this gets a lot more difficult if > it has to be done from the other side. http://ftp.zresearch.com/pub/gluster/glusterfs/1.3/glusterfs-1.3.8pre6.tar.gz Also what do you mean by "but this gets a lot more difficult if > it has to be done from the other side." Krishna On Wed, Apr 23, 2008 at 4:45 PM, Gareth Bult <gareth@xxxxxxxxxxxxx> wrote: > Hi, > > Which node are you mounting against? > If each node mounts against the local server, you might like to check out this bug; > http://savannah.nongnu.org/bugs/?21918 > > It's been outstanding for nearly 4 months and there's no indication this issue has been addressed. Essentially to ensure a consistent view, all clients need to mount against the same server .. which is sort of Ok as they should both fail-over to the (same) next available node in the event of a server crash. > > hth > > Gareth. > > > > > ----- Original Message ----- > From: gordan@xxxxxxxxxx > To: gluster-devel@xxxxxxxxxx > Sent: Wednesday, April 23, 2008 11:05:17 AM GMT +00:00 GMT Britain, Ireland, Portugal > Subject: Replication resync after disconnection > > Hi, > > I have two nodes in AFR mode. If node2 down and I add files to node1, when > the node2 comes up, it cannot see the files. ls doesn't show them. > > However, after I cat/head the files on node1, they appear on node2. > > Is there a way to make this work? I can live with head-ing every file when > a node comes up to force a resync, but this gets a lot more difficult if > it has to be done from the other side. > > I initially thought this was a problem caused by lack of xattr support on > reiser4 (node2 was on reiser4), but I've since converted it to ext3, and > I'm still seeing the same behaviour. > > Gordan > > > _______________________________________________ > Gluster-devel mailing list > Gluster-devel@xxxxxxxxxx > http://lists.nongnu.org/mailman/listinfo/gluster-devel > > > _______________________________________________ > Gluster-devel mailing list > Gluster-devel@xxxxxxxxxx > http://lists.nongnu.org/mailman/listinfo/gluster-devel >
