Re: Clarification on common tasks

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

 




----- Original Message -----
> From: "Gandalf Corvotempesta" <gandalf.corvotempesta@xxxxxxxxx>
> To: "Lindsay Mathieson" <lindsay.mathieson@xxxxxxxxx>
> Cc: "Anuradha Talur" <atalur@xxxxxxxxxx>, "gluster-users" <Gluster-users@xxxxxxxxxxx>
> Sent: Friday, August 12, 2016 2:48:37 AM
> Subject: Re:  Clarification on common tasks
> 
> 2016-08-11 16:13 GMT+02:00 Gandalf Corvotempesta
> <gandalf.corvotempesta@xxxxxxxxx>:
> > # gluster volume heal gv0 info heal-failed
> > Gathering list of heal failed entries on volume gv0 has been
> > unsuccessful on bricks that are down. Please check if all brick
> > processes are running.
> 
> Healing is now complete:
> 
> # gluster volume heal gv0 info
> Brick 1.2.3.112:/export/brick1/brick
> Status: Connected
> Number of entries: 0
> 
> Brick 1.2.3.113:/export/sdb1/brick
> Status: Connected
> Number of entries: 0
> 
> Brick 1.2.3.114:/export/sdb1/brick
> Status: Connected
> Number of entries: 0
> 
> I remember that there was some errors during healing, so i've tried to run
> this:
> 
> # gluster volume heal gv0 info heal-failed
> Gathering list of heal failed entries on volume gv0 has been
> unsuccessful on bricks that are down. Please check if all brick
> processes are running.
Actually info healed and heal-failed are deprecated. Recently some changes
were made due to which wrong error message is being given to the users.
A bug has been raised for the same and will be worked on for the next releases.
> 
> but all bricks are up and running:
> 
> # gluster volume status
> Status of volume: gv0
> Gluster process                             TCP Port  RDMA Port  Online  Pid
> ------------------------------------------------------------------------------
> Brick 1.2.3.112:/export/brick1/brick    49153     0          Y       11222
> Brick 1.2.3.113:/export/sdb1/brick      49152     0          Y       5786
> Brick 1.2.3.114:/export/sdb1/brick      49152     0          Y       920
> Self-heal Daemon on localhost           N/A       N/A        Y       11227
> Self-heal Daemon on 1.2.3.113           N/A       N/A        Y       31559
> Self-heal Daemon on 1.2.3.114           N/A       N/A        Y       26173
> 
> Task Status of Volume gv0
> ------------------------------------------------------------------------------
> There are no active volume tasks
> 
> 
> 
> Why i'm unable to see what happened during healing ? I can't use any
> of "healed" or "heal-failed" arguments.
> "split-brain" works.

> 
> Any suggestion? I'm curious to see why some files triggered an heal failure.
You can get glustershd logs to see why heals failed. If you need help with it,
please give us the log files.
> 

-- 
Thanks,
Anuradha.
_______________________________________________
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