I wanted to put this idea for the larger community to discuss/debate
How about an on-demand scrubbing feature where I can provide a list of
files or dir and BitRot can scan/scrub it for corruption.
Again, this will be implemented just as another policy, which can be
set/unset by the user/admin
I
Thanks Venky, I also wanted to put forward how this can help in a
openstack/cloud env.
where we have 2 distinct admin roles (virt/openstack admin and storage
admin)
1) Gluster volume 'health' should display the health status (OK, warn,
fatal/error etc)
2) Based on that the admin can query
On Fri, Nov 28, 2014 at 10:00 PM, Vijay Bellur vbel...@redhat.com wrote:
On 11/28/2014 08:30 AM, Venky Shankar wrote:
[snip]
1. Can the bitd be one per node like self-heal-daemon and other global
services? I worry about creating 2 * N processes for N bricks in a node.
Maybe we can consider
On 11/28/2014 08:30 AM, Venky Shankar wrote:
[snip]
1. Can the bitd be one per node like self-heal-daemon and other global
services? I worry about creating 2 * N processes for N bricks in a node.
Maybe we can consider having one thread per volume/brick etc. in a single
bitd process to make it
On 10/31/2014 04:09 PM, Venky Shankar wrote:
Hey folks,
Myself and Raghavendra (@rabhat) have been discussing about BitRot[1]
and came up with a list of high level tasks (breakup items) captured
here[2]. The pad will be updated on an ongoing basis reflecting the
current status/items that are
Thanks Xavi.
- Original Message -
From: Xavier Hernandez xhernan...@datalab.es
To: Alok Srivastava asriv...@redhat.com, Venky Shankar
vshan...@redhat.com
Cc: gluster-devel@gluster.org, Ric Wheeler rwhee...@redhat.com
Sent: Thursday, November 6, 2014 9:15:52 PM
Subject: Re: [Gluster-devel
Thanks Venky for sharing the details.
I have included Pranith and Atin for a specific question:
With current implementation of erasure coding, Do we have the capability of
detecting and correcting bit rot?
Let's say we have fragments of a file on multiple bricks and a read request is
sent to
Hi Alok,
On 11/06/2014 02:53 PM, Alok Srivastava wrote:
Thanks Venky for sharing the details.
I have included Pranith and Atin for a specific question:
With current implementation of erasure coding, Do we have the capability of
detecting and correcting bit rot?
Current implementation of
Hey folks,
Myself and Raghavendra (@rabhat) have been discussing about BitRot[1]
and came up with a list of high level tasks (breakup items) captured
here[2]. The pad will be updated on an ongoing basis reflecting the
current status/items that are being worked on. As always, contributions
in