[Gluster-devel] Force issue

[Paul Cuzner]

Bit of a delay on this one (on hols), but +1 from me 

I use the force parameter in gluster-deploy - specifically for enabling snapshot support by provisioning thin LV's. 

PC 

----- Original Message -----

> From: "James" <purpleidea at gmail.com>
> To: "Gluster Devel" <gluster-devel at nongnu.org>
> Sent: Saturday, 11 January, 2014 6:50:50 PM
> Subject: [Gluster-devel] Force issue

> I came across this issue while working on Puppet Gluster...

> volume create: puppet: failed: The brick
> annex1.example.com:/var/lib/puppet/tmp/gluster/data/puppet is is being
> created in the root partition. It is recommended that you don't use
> the system's root partition for storage backend. Or use 'force' at the
> end of the command if you want to override this behavior.

> For automation purposes, this is a problem, because while I'm happy to
> add in the 'force' argument for all commands to avoid the above error,
> if a different type of error that can be overrided by force occurs,
> then I'll be unknowingly allowing it.

> For this reason, it probably makes sense to add in an alternate
> syntax, such as --allow-root-storage or similar... One for each
> possible override.

> Also:

> As a side note, I would _LOVE_ to see an --allow-reusing-prefix to
> forcibly clear the prefixes if they are empty and create the volume.
> The problem is failed gluster volume create commands make folders on
> all the hosts, and cause you to hit the prefix problem.

> Cheers,
> James

> _______________________________________________
> Gluster-devel mailing list
> Gluster-devel at nongnu.org
> https://lists.nongnu.org/mailman/listinfo/gluster-devel
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://supercolony.gluster.org/pipermail/gluster-devel/attachments/20140120/91b5b088/attachment-0001.html>