Hi David,
I have also tested the bitrot signature process by default it takes < 250
KB/s.
regards
Amudhan P
On Fri, Mar 1, 2019 at 1:19 PM David Spisla wrote:
> Hello folks,
>
> I did some observations concerning the bitrot daemon. It seems to be that
> the bitrot signer is signing files
Hello folks,
I did some observations concerning the bitrot daemon. It seems to be that
the bitrot signer is signing files depending on file size. I copied files
with different sizes into a volume and I was wonderung because the files
get their signature not the same time (I keep the expiry time
Orig file structure to share with gluster is /foo
Volname is testvol
Data exists in foo . You have 2 copies, one on machine a, another on b.
When you create the testvol in gluster, it creates a folder /foo/.glusterfs and
writes all gluster metadata there. There's config data written in gluster
On Thu, Feb 28, 2019, 8:44 PM Tami Greene wrote:
> I'm missing some information about how the cluster volume creates the
> metadata allowing it to see and find the data on the bricks. I've been
> told not to write anything to the bricks directly as the glusterfs cannot
> create the metadata and
I'm missing some information about how the cluster volume creates the
metadata allowing it to see and find the data on the bricks. I've been
told not to write anything to the bricks directly as the glusterfs cannot
create the metadata and therefore the data doesn't exist in the cluster
world.
hi everyone
I'm hoping devel might be reading this, but if not - anybody tried
glusterfs off PyPy?
If yes and it works then what was/is the experience?
many thanks, L.
pEpkey.asc
Description: application/pgp-keys
___
Gluster-users mailing list
