For what it's worth, I disabled quotas and re-enabled them. This of course
caused the limits I had set to be erased and GlusterFS to re-run the
find/stat on all bricks. Once it finished I was able to add a limit and it
was finally accurate.
I'm still hoping someone can comment about this. Is it
Hi Xavi,
I am working with a distributred-replicated volume. What I've been doing is
copying the shards from each node to their own "recovery" directory, discarding
shards that are 0 bytes, then comparing the remainder and combining unique
shards into a common directory. Then I'd build a
Hi Anthony,
On Tue, Sep 7, 2021 at 8:20 PM Anthony Hoppe wrote:
> I am currently playing with concatenating main file + shards together. Is
> it safe to assume that a shard with the same ID and sequence number
> (5da7d7b9-7ff3-48d2-8dcd-4939364bda1f.242 for example) is identical across
>
