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 request. "Dr. J?rg Petersen" <joerg.h.petersen at googlemail.com> wrote: >Hello, > > 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 >.gluster-Directory. >Since btrfs is painfully slow in deleting, I would prefer an option to >reuse the Content, wich should be valid for the new (Snapshot-) >Gluster-Volume... > >Greetings, >J?rg > > >Am 20.09.2012 20:56, schrieb Doug Hunley: >> On Thu, Sep 20, 2012 at 2:47 PM, Joe Julian <joe at julianfamily.org> wrote: >>> 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 often >>> 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.. >> >
