glusterfs

History

Sanju Rakonde 90922d20f5 glusterd: get-state command should not fail if any brick is gone bad

Problem: get-state command will error out, if any of the underlying
brick(s) of volume(s) in the cluster go bad.

It is expected that get-state command should not error out, but
should generate an output successfully.

Solution: In glusterd_get_state(), a statfs call is made on the
brick path for every bricks of the volumes to calculate the total
and free memory available. If any of statfs call fails on any
brick, we should not error out and should report total memory and free
memory of that brick as 0.

This patch also handles a statfs failure scenario in
glusterd_store_retrieve_bricks().

fixes: bz#1672205

Change-Id: Ia9e8a1d8843b65949d72fd6809bd21d39b31ad83
Signed-off-by: Sanju Rakonde <srakonde@redhat.com>

2019-02-05 14:40:25 +00:00

cluster

cluster/dht: Do not use gfid-req in fresh lookup

2019-02-02 03:09:36 +00:00

debug

Don't depend on string options to be valid always

2018-12-17 17:19:00 +00:00

features

core: make gf_thread_create() easier to use

2019-02-01 10:37:20 +01:00

lib/src

Multiple files: reduce work while under lock.

2019-01-29 09:27:22 +00:00