Re: Has something broken with the -s option in the git builds?

["Amar S. Tumballi" <amar@xxxxxxxxxxxxx>]

Yes, with latest git, you are required to keep all the fetchable files same in all servers. This is because of a possibility where you have more than one machine serving volume files, and if they are different (say one uses replicate, another stripe), there is a high chance that we will messup the backend.

Hence this checksum protection for files fetched from server now. Either you can keep all the files same, or keep the files only on one server.

Regards,
Amar

On Fri, Mar 6, 2009 at 10:37 AM, Paul Rawson <plrca2@xxxxxxxxx> wrote:

I've been using glusterfs -s server /glusterfs and just recently it's stopped working. The following is in the logs:

 

2009-03-06 10:34:10 E [client-protocol.c:5912:client_setvolume_cbk] client101-0: SETVOLUME on remote-host failed: volume-file checksum varies from earlier access
2009-03-06 10:34:10 C [fuse-bridge.c:2662:notify] fuse: remote volume file changed, try re-mounting
2009-03-06 10:34:10 W [glusterfsd.c:811:cleanup_and_exit] glusterfs: shutting down
2009-03-06 10:34:10 W [fuse-bridge.c:2903:fini] fuse: unmounting '/glusterfs'

glusterfs -f configfile does still work though.

 

Thanks,

-Paul
--
Got r00t?

_______________________________________________
Gluster-devel mailing list
Gluster-devel@xxxxxxxxxx
http://lists.nongnu.org/mailman/listinfo/gluster-devel

-- 
Amar Tumballi