Thanks Justin, that looks good. As an aside, is it true to say that you really only need to update the config files on a single server and remove the configuration files completely from the peers before starting the glusterd daemons and it should all work? I tried this with 2 servers, on one I cleared the /var/lib/glusterd directory and started glusterd. on the other I made the hostname changes, started glusterd and mounted the fs from a client and all was well. I noticed that the config files reappeared on the peer after a while. On Tue, 2014-01-07 at 15:45 +0000, Justin Clift wrote: > On Tue, 07 Jan 2014 18:31:58 +0800 > Franco Broi <franco.broi@xxxxxxxxxx> wrote: > > > > The brick filename specified in file "/path.../filename" does not exist > > in the brick directory "/path/...". > > Sure. How does this look? > > https://bugzilla.redhat.com/show_bug.cgi?id=1049481 > > > > A utility to change the hostname would be useful too... > > That's not a bad idea too. Just added a feature request for that > as well: > > https://bugzilla.redhat.com/show_bug.cgi?id=1049470 > > Hopefully it gets looked at and coded up in time for the next > major release or so. :) > > Regards and best wishes, > > Justin Clift > _______________________________________________ Gluster-users mailing list Gluster-users@xxxxxxxxxxx http://supercolony.gluster.org/mailman/listinfo/gluster-users
