[Gluster-users] add/replace brick corrupting data

[Krutika Dhananjay]

Hmm in that case, could you do the following:


If you could recreate this issue again, could you record the extended
attributes associated with
the shards that you see being listed against the replaced-brick in
heal-info.
For example, assuming you replaced the brick on vng, once heal kicks in,
when you start to see
entries/shards listed under vng also (indicating that vng is the src and
vna and vnb are sinks), could you go to the individual bricks and quickly
capture the output of the following command for each of the entries listed:

# getfattr -d -m . -e hex
<brick-path>/<path-to-the-shard-or-file-or-dir-getting-listed-for-reverse-heal-in-heal-info-output>

and attach them in your reply?

-Krutika

On Tue, May 17, 2016 at 4:44 PM, Lindsay Mathieson <
lindsay.mathieson at gmail.com> wrote:

> On 17/05/2016 7:56 PM, Krutika Dhananjay wrote:
>
> Would you know where the logs of individual vms are with proxmox?
>
>
> No i don't I'm afraid. Would they be a function of gluster or qemu?
>
>
> --
> Lindsay Mathieson
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://www.gluster.org/pipermail/gluster-users/attachments/20160517/d2f6ead9/attachment.html>