mgmt/glusterd: do not use the root of the snaped device as the brick path

Suppose a volume's brick has the path /export/brick/vol/dir and lvm
of that brick is mounted at /export. Now snap of that brick is
taken, and is mounted on a path (say /run/gluster/snaps/<snapname>)
While creating the brick for the snap volume, /run/gluster/snaps/<snapname>
(i.e the mount point of the snap lvm) should not be used as the export
directory. The directory path remaining after the mount point of the
original lvm should be appended to the snap lvm mounted path and
should be used as the export directory
(ex: /run/gluster/snaps/<snapname>/brick/vol/dir in this case).
Its because the volume-id of the original volume and other extended
attributes wont be set on the root. It will be in the same path as the
original lvm.

Change-Id: I832dac8478eba1a318bdbcdf6cd8bf55b2a3261d
Signed-off-by: Raghavendra Bhat <raghavendra@redhat.com>

0 files changed, 0 insertions, 0 deletions