[Gluster-users] Gluster 3.4.2 on Ubuntu 12.04 LTS Server - Upstart No Go

[Matt Edwards]

I could be completely off-base, but were you trying to mount with noatime?

I ran into a similar problem where, after upgrading to 3.4.2, all my client
mounts failed.  I discovered (by accident) that it was only due to
incompatible mount options (namely noatime).  In previous versions, the
client just gave a warning message about unsupported options, but now it
fails without mentioning the cause.  I believe there is a bug report for
this issue (that I discovered afterwards).

Anyways, I thought this had a chance of being the issue, but maybe it's
something different in your case.

Matt


On Tue, Mar 4, 2014 at 2:09 PM, Brock Nanson <brock at nanson.net> wrote:

> I thought I would share my experience in case it helps someone else avoid
> a bruised forehead.
>
> I'm running the semiosis Gluster 3.4.2 on Ubuntu 12.04 (two nodes,
> replicated) as server and client on both.  Going through all the typical
> configuration work, all seemed good.  The problem came when I tried to get
> the boxes to start Gluster and mount the volume at boot... without user
> intervention.  Thinking that the most difficult part of the installation
> should be configuring Gluster (newbie to distributed file systems in
> general, never used Gluster before), I foolishly wasted a pile of time
> trying to fix the *simple* boot problem.  Well, I did fix it, but only by
> finally disabling the upstart files bundled in the install
> (glusterfs-server.conf and mounting-glusterfs.conf).
>
> This was a clean install of Ubuntu 12.04.  Actually, two clean installs
> for testing.  And then another clean install on one box to rule out the
> original install!  Same behaviour on all installs.
>
> I spent some time experimenting with different fstab entries and found I
> could change the mount behaviour, but only to determine *when* the mount
> would fail... it always failed!
>
> My solution was to disable the two Gluster upstart conf files with
> .override files containing 'manual'.  Then a simple script to a) start
> glusterfs-server; b) sleep for a few seconds; c) mount the Gluster volume.
>  The script is called from rc.local.
>
> Hardly an elegant solution I know, but at some point *'works'* beats *'pretty
> but non-functional'*.
>
> It's possible there is something quirky with my install that could be
> responsible.  But given that other than installing and configuring Gluster,
> nothing on the servers was tweaked, I'm thinking there is a problem with
> the Gluster upstart conf files.  Or something in 12.04 has rendered them
> inoperable. Or maybe it's as a friend in Poland says... (direct
> translation) "it's the Malice of Things..."  Truly a better description
> than anything we have in English! ;-)
>
> I'm not looking for a solution unless someone has an obvious fix that
> Google couldn't locate.  I have a quick and dirty work around that works.
>  I just hope to save someone else the pain.
>
> _______________________________________________
> Gluster-users mailing list
> Gluster-users at gluster.org
> http://supercolony.gluster.org/mailman/listinfo/gluster-users
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://supercolony.gluster.org/pipermail/gluster-users/attachments/20140304/dd01679d/attachment.html>