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

[Brian Candler]

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.

https://bugzilla.redhat.com/show_bug.cgi?id=839021

[2012-07-10 18:25:57.804526] E [posix.c:3930:init] 0-single1-posix: Directory '/disk/storage1/single1' doesn't exist, exiting.

Cheers,

Brian.