The clients should be enough. But seeing as you mount didn't even happen, there might be some other problem. As Amar suggested, could you let us know what's in the client logs? They should be in /var/log/glusterfs/<mnt-point>.log. Thanks, Kaushal On Fri, May 4, 2012 at 11:17 AM, Toby Corkindale < toby.corkindale at strategicdata.com.au> wrote: > On 04/05/12 15:37, Kaushal M wrote: > >> Hi Toby. >> >> This is the correct way to do it and it should work. >> >> However, there was a bug reported earlier where the outputs of mount/df >> command showed the original server even when the backup server was used >> for gluster mounts. This bug doesn't happen anymore on the latest qa >> release. >> > > Hi Kaushal, > I don't think that's the same bug. I can't even mount it. (There is > nothing listed in /proc/mounts, for instance) > > > I believe you are testing with 3.3 beta 3. Could you check with the >> latest 3.3.0qa release (src tarball here >> http://bits.gluster.com/pub/**gluster/glusterfs/src/** >> glusterfs-3.3.0qa39.tar.gz<http://bits.gluster.com/pub/gluster/glusterfs/src/glusterfs-3.3.0qa39.tar.gz> >> , no debs) and see if the problem still exists? >> > > Ah, ok, I'll have a go with that -- do I need that on the servers too, or > just the client? > > -Toby > -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://gluster.org/pipermail/gluster-users/attachments/20120504/414eb234/attachment.htm>
