[Bugs] [Bug 1414287] repeated operation failed warnings in gluster mount logs with disperse volume

bugzilla at redhat.com bugzilla at redhat.com
Tue Feb 21 13:01:17 UTC 2017


https://bugzilla.redhat.com/show_bug.cgi?id=1414287



--- Comment #12 from Pranith Kumar K <pkarampu at redhat.com> ---
(In reply to Ashish Pandey from comment #11)
> Pranith,
> 
> While working on one of my patch, I observed that when all the bricks are UP
> and everything is fine, heal info was listing entries for one of the random
> brick while IO was going on.
> 
> I removed following patch -
> https://review.gluster.org/#/c/16377/ and then did not observe this issue.
> 
> I think the above patch is causing some issue.
> Even with the latest patch sent by you https://review.gluster.org/16468 , I
> am seeing these entries.
> 
> 
> Steps - 
> 
> 1 - create a volume with or without your patch-
> 2 - mount the volume and start creating files on mount point using following
> command - 
> for i in {1..10000}; do dd if=/dev/zero of=test-$i count=1 bs=1M; done
> 
> 3 - Watch heal info from different terminal.
> watch gluster v heal vol info
> 
>  
> [root at apandey glusterfs]# gluster v heal vol info
> Brick apandey:/brick/gluster/vol-1
> /test-379 
> /test-357 
> /test-350 
> /test-397 
> /test-333 
> /test-394 
> /test-371 
> /test-355 
> /test-339 
> /test-359 
> /test-336 
> /test-318 
> /test-348 
> /test-367 
> /test-356 
> /test-335 
> /test-384 
> /test-395 
> /test-389 
> /test-380 
> /test-330 
> /test-385 
> /test-329 
> /test-368 
> /test-337 
> /test-340 
> /test-341 
> /test-332 
> /test-402 
> /test-386 
> /test-353 
> /test-361 
> /test-382 
> /test-401 
> /test-362 
> /test-393 
> /test-372 
> /test-381 
> /test-390 
> /test-370 
> /test-369 
> /test-399 
> /test-375 
> /test-377 
> /test-343 
> /test-364 
> /test-351 
> /test-363 
> /test-354 
> /test-331 
> /test-346 
> /test-378 
> /test-342 
> /test-338 
> /test-396 
> /test-365 
> /test-376 
> /test-383 
> /test-360 
> /test-347 
> /test-373 
> /test-392 
> /test-400 
> /test-349 
> /test-352 
> /test-345 
> /test-334 
> /test-391 
> /test-366 
> /test-387 
> /test-344 
> /test-388 
> /test-358 
> /test-374 
> /test-398 
> Status: Connected
> Number of entries: 75
> 
> Brick apandey:/brick/gluster/vol-2
> Status: Connected
> Number of entries: 0
> 
> Brick apandey:/brick/gluster/vol-3
> Status: Connected
> Number of entries: 0
> 
> Brick apandey:/brick/gluster/vol-4
> Status: Connected
> Number of entries: 0
> 
> Brick apandey:/brick/gluster/vol-5
> Status: Connected
> Number of entries: 0
> 
> Brick apandey:/brick/gluster/vol-6
> Status: Connected
> Number of entries: 0

Good catch. Let me try and fix this too.

-- 
You are receiving this mail because:
You are on the CC list for the bug.
Unsubscribe from this bug https://bugzilla.redhat.com/token.cgi?t=POeQbmNJ6m&a=cc_unsubscribe


More information about the Bugs mailing list