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

[Lonni J Friedman]

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?

thanks