Page History

...

root@willis-k8-test-gluster:/# gluster volume list
ndslabs
root@willis-k8-test-gluster:/# gluster volume status
Volume ndslabs is not started

...

Reusing a Volume

WARNING: Restarting the DaemonSet after the initial volume creation will invalidate any bricks created. We still need to figure out how to reuse data from previous bricks that are no longer accessible.

To use the same path, it may be necessary to delete a previous brick directory and recreate it.

Simply add force to the end of your volume create command to force GlusterFS to reuse a volume that is no longer accessible:

root@willis-k8-test-gluster:/# gluster volume create ndslabs transport tcp 192.168.100.89:/media/brick0/brick/ndslabs 192.168.100.156:/media/brick0/brick/ndslabs
volume create: ndslabs: failed: /media/brick0/brick/ndslabs is already part of a volume
root@willis-k8-test-gluster:/# gluster volume create ndslabs transport tcp 192.168.100.89:/media/brick0/brick/ndslabs 192.168.100.156:/media/brick0/brick/ndslabs force
volume create: ndslabs: success: please start the volume to access data

The alternative solution would be to delete / recreate the mount pointThis can be done using the following commands:

root@willis-k8-test-gluster:/# rm -rf /path/to/brick0
root@willis-k8-test-gluster:/# mkdir -p /path/to/brick0

...