Wait for a brick's local filesystem to be mounted before starting.

Summary: By far the most common reason why a brick's directory might not exist is that the local filesystem on which it lives hasn't finished mounting yet.  This is unlike other checks we do, such as for a volume ID and GFID.  Some of these are normal conditions when a brick is firstcreated; others are often the result of operator/script error.  In the singular case of the directory being absent, wait a little while to see if it comes up.

Test Plan:
Create a volume.
Start/stop a volume once so everything gets initialized.
Move a brick directory out of place.
Try to start the volume.  This should pause.
Immediately move the brick directory back into place.   This should break the pause.

Reviewers: #posix_storage, sshreyas

Reviewed By: sshreyas

Subscribers: shreyas, sshreyas, ventullo, moox

Differential Revision: https://phabricator.intern.facebook.com/D5063515

Tags: gluster

Change-Id: Ied7b07b1a60f54856a67d4cdbad35bfce9e196e4
Signed-off-by: Jeff Darcy <jdarcy@fb.com>
Reviewed-on: https://review.gluster.org/18274
Reviewed-by: Jeff Darcy <jeff@pl.atyp.us>
Tested-by: Jeff Darcy <jeff@pl.atyp.us>
CentOS-regression: Gluster Build System <jenkins@build.gluster.org>
Smoke: Gluster Build System <jenkins@build.gluster.org>

0 files changed, 0 insertions, 0 deletions