Re: add/replace brick corrupting data

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



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@xxxxxxxxx> 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

_______________________________________________
Gluster-users mailing list
Gluster-users@xxxxxxxxxxx
http://www.gluster.org/mailman/listinfo/gluster-users

[Index of Archives]     [Gluster Development]     [Linux Filesytems Development]     [Linux ARM Kernel]     [Linux ARM]     [Linux Omap]     [Fedora ARM]     [IETF Annouce]     [Bugtraq]     [Linux OMAP]     [Linux MIPS]     [eCos]     [Asterisk Internet PBX]     [Linux API]

  Powered by Linux