Hi
What will happen if we format the volume where the bricks of replicate
gluster volume's are created and restart the glusterd on both node.
It will work fine or in this case need to remove /var/lib/glusterd
directory as well.
--
Regards
Abhishek Paliwal
This would erase the xattrs set on the brick root (volume-id), which
identify it as a brick. Brick processes will fail to start when this
xattr isn't present.
On Fri, May 20, 2016 at 3:42 PM, ABHISHEK PALIWAL
wrote:
> Hi
>
> What will happen if we format the volume
> As a community
> if we would like to increase adoption of Gluster I think it would be
> good if other languages could produce bindings in their native language
> without needing to use the C libraries. If I'm writing code in Java or
> Rust or (name your language here) and I see a Gluster
On 05/19/2016 10:25 PM, Pranith Kumar Karampuri wrote:
Once every 3 months i.e. option 3 sounds good to me.
+1 from my end.
Every 2 months seems to be a bit too much, 4 months is still fine, but
gives us 1 in 3 to pick the LTS, I like 1:4 odds better for the LTS,
hence the 3 months (or
I am not getting any failure and after restart the glusterd when I run
volume info command it creates the brick directory
as well as .glsuterfs (xattrs).
but some time even after restart the glusterd, volume info command showing
no volume present.
Could you please tell me why this unpredictable
On 05/20/2016 08:13 PM, Angelos SAKELLAROPOULOS wrote:
Hi,
May I ask why following review requests are not submitted to
release-3.6 ?
It seems that they fail in netbsd, freebsd smoke tests which are not
related to code changes.
You'd have to re-trigger tests if they are spurious failures.
On Fri, May 20, 2016 at 05:43:07PM +0300, Angelos SAKELLAROPOULOS wrote:
> May I ask why following review requests are not submitted to release-3.6 ?
> It seems that they fail in netbsd, freebsd smoke tests which are not
> related to code changes.
There are build errors. I am note sur how you