[Gluster-users] cannot create a new volume with a brick that used to be part of a deleted volume?

[Lonni J Friedman]

Hi Harry,
Thanks for your reply.  I tried to manually delete everything from the
brick filesystems (including the hidden files/dirs), but that didn't
help:
########
[root at farm-ljf0 ~]# ls -la /mnt/sdb1/
total 4
drwxr-xr-x  2 root root  6 Sep 18 11:22 .
drwxr-xr-x. 3 root root 17 Sep 13 09:45 ..
[root at farm-ljf0 ~]# gluster volume create gv0 rep 2 transport tcp
10.31.99.165:/mnt/sdb1 10.31.99.166:/mnt/sdb1
/mnt/sdb1 or a prefix of it is already part of a volume
#########

So I unmounted, formatted fresh, remounted, and then the volume
creation worked.  This seems like a bug, or at the very least a
shortcoming in the documentation (which never mentions any of these
requirements).

Anyway, thanks for the help, its got me back on track.  Hopefully
someone from the gluster team will comment on this.


On Tue, Sep 18, 2012 at 11:18 AM, harry mangalam <harry.mangalam at uci.edu> wrote:
> I believe gluster writes 2 entries into the top level of your gluster brick
> filesystems:
>
> -rw-r--r--   2 root root    36 2012-06-22 15:58 .gl.mount.check
> drw------- 258 root root  8192 2012-04-16 13:20 .glusterfs
>
> You will have to remove these as well as all the other fs info from the volume
> to re-add the fs as another brick.
>
> Or just remake the filesystem - instantaneous with XFS, less so with ext4.
>
> hjm
>
> On Tuesday, September 18, 2012 11:03:35 AM Lonni J Friedman wrote:
>> Greetings,
>> I'm running v3.3.0 on Fedora16-x86_64.  I used to have a replicated
>> volume on two bricks.  This morning I deleted it successfully:
>> ########
>> [root at farm-ljf0 ~]# gluster volume stop gv0
>> Stopping volume will make its data inaccessible. Do you want to
>> continue? (y/n) y
>> Stopping volume gv0 has been successful
>> [root at farm-ljf0 ~]# gluster volume delete gv0
>> Deleting volume will erase all information about the volume. Do you
>> want to continue? (y/n) y
>> Deleting volume gv0 has been successful
>> [root at farm-ljf0 ~]# gluster volume info all
>> No volumes present
>> ########
>>
>> I then attempted to create a new volume using the same bricks that
>> used to be part of the (now) deleted volume, but it keeps refusing &
>> failing claiming that the brick is already part of a volume:
>> ########
>> [root at farm-ljf1 ~]# gluster volume create gv0 rep 2 transport tcp
>> 10.31.99.165:/mnt/sdb1 10.31.99.166:/mnt/sdb1
>> /mnt/sdb1 or a prefix of it is already part of a volume
>> [root at farm-ljf1 ~]# gluster volume info all
>> No volumes present
>> ########
>>
>> Note farm-ljf0 is 10.31.99.165 and farm-ljf1 is 10.31.99.166.  I also
>> tried restarting glusterd (and glusterfsd) hoping that might clear
>> things up, but it had no impact.
>>
>> How can /mnt/sdb1 be part of a volume when there are no volumes present?
>> Is this a bug, or am I just missing something obvious?