[Gluster-users] Unexpected Gluster behavior on startup without backing stores mounted

[Whit Blauvelt]

On Fri, Sep 07, 2012 at 07:32:14AM +0100, Brian Candler wrote:
> On Thu, Sep 06, 2012 at 03:19:53PM -0400, Whit Blauvelt wrote:
> > Here's the unexpected behavior: Gluster restored the nfs export based on the
> > backing store. But without that backing store really mounted, it used
> > /mnt/xyz, which at that point was a local subdirectory of /. This is not
> > optimal. An error or warning or refusal to run would be preferable to
> > presenting the export when the "real" backing store has gone missing.
> 
> For a different reason, I have been using a subdirectory of the mountpoint
> for the brick - e.g. if the filesystem is /mnt/xyz then I have done
> mkdir /mnt/xyz/brick1 and set the brick as server1:/mnt/xyz/brick1
> 
> However I think this also fixes your problem, because if you try to mount
> when the brick1 directory is not present, the glusterfsd process doesn't
> start.  The client doesn't get a good error message, but buried in the
> server logs you can see what happened.

I like that. And never would have thought of it. Thanks Brian!

Whit