Hi Strahil,
Thanks for the response, appreciate it.
There were two set sets of shard files (each set of two replicas and the
arbiter data) showing up, one 0-byte set and one of the correct size, for the
problem data. The correct data looked fine. The two sets of shard files is what
was
I skimmed over , so take everything I say with a grain of salt.
Based on thr logs, the gfid for one of the cases is clear ->
b42dc8f9-755e-46be-8418-4882a9f765e1 and shard 5613.
As there is a linkto, most probably the shards location was on another
subvolume and in such case I would just "walk"
Hi,
We have a 4 x ( 2 + 1 ) distribute-replicate volume with sharding enabled. We
use the volume for storing backing files for iscsi devices. The iscsi devices
are provided to our file server using tgtd using the glfs backing store type
via libgfapi.
So we had a problem the other day where
