[Gluster-users] cannot create a new volume with a brick that used to be part of a deleted volume?
doug.hunley at gmail.com
Fri Sep 21 19:24:07 UTC 2012
Yes, I think an option (--force maybe) that says "I know I'm about to lose
data, that's what I want" sounds like a reasonable compromise. And the
given examples have clarified the current behavior in my mind. Thank you
for the replies everyone. I'm better informed now.
Sent from my Google Nexus 7
On Sep 21, 2012 2:11 AM, "Joe Julian" <joe at julianfamily.org> wrote:
> Adding a --yes-i-know-what-im-doing type option is something I would get
> behind (and have suggested, myself). File a bug report as an enhancement
> "Dr. Jörg Petersen" <joerg.h.petersen at googlemail.com> wrote:
> > what I regularly do:
> >1) Create a snapshot (btrfs) of Brick
> >2) reassemble the snapshots into an new (Snapshot-) Gluster-Volume
> >When Reassembling the snapshots I have to remove all xattr's and
> >Since btrfs is painfully slow in deleting, I would prefer an option to
> >reuse the Content, wich should be valid for the new (Snapshot-)
> >Am 20.09.2012 20:56, schrieb Doug Hunley:
> >> On Thu, Sep 20, 2012 at 2:47 PM, Joe Julian <joe at julianfamily.org>
> >>> Because it's a vastly higher priority to preserve data. Just because I
> >>> delete a volume doesn't mean I want the data deleted. In fact, more
> >>> than not, it's quite the opposite. The barrier to data loss is high,
> and it
> >>> should remain high.
> >> OK, again I'll ask: what is a typical scenario for me as a gluster
> >> admin to delete a volume and want to add one (or more) of its former
> >> bricks to another volume and keep that data in tact? I can't think of
> >> a real world example. But I assume they exist as this is the model
> >> taken by gluster..
> Gluster-users mailing list
> Gluster-users at gluster.org
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the Gluster-users