[Bugs] [Bug 1783858] New: Heal Info is hung when I/O is in progress on a gluster block volume

bugzilla at redhat.com bugzilla at redhat.com
Mon Dec 16 05:37:31 UTC 2019


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

            Bug ID: 1783858
           Summary: Heal Info is hung when I/O is in progress on a gluster
                    block volume
           Product: GlusterFS
           Version: 7
            Status: NEW
         Component: replicate
          Keywords: Reopened, Triaged
          Assignee: bugs at gluster.org
          Reporter: ravishankar at redhat.com
                CC: bugs at gluster.org
        Depends On: 1774011
  Target Milestone: ---
    Classification: Community



+++ This bug was initially created as a clone of Bug #1774011 +++

This bug was initially created as a copy of Bug #1721355

I am copying this bug because: 
I'd like to send a patch against it.


Description of problem:
I was observing this issue while working on BZ 1707259. 
When there is no self-heals pending, but there are a lot of I/Os happening on a
replicate volume with gluster block profile enabled, heal-info was hung. The
moment I/O stopped, the command completed successfully. I'm guessing it has
something to do with eager locking but I need to RCA it.

Version-Release number of selected component (if applicable):
rhgs-3.5.0

How reproducible:
Always on my dev VMs.

Steps to Reproduce:
- Create a 1x3 replica volume (3 node setup)
- Apply  gluster-block profile on the volume. (gluster v set $volname group
gluster-block)
- Mount a fuse client on another node and run parallel 'dd's :
for i in seq{1..20}; do dd if=/dev/urandom of=FILE_$i bs=1024 count=102400&
done
- After 10-20 seconds while the I/O is going on, run heal-info command - It
will be hung.


Actual results:
heal info command is hung

Expected results:
It should not be hung.


Referenced Bugs:

https://bugzilla.redhat.com/show_bug.cgi?id=1774011
[Bug 1774011] Heal Info is hung when I/O is in progress on a gluster block
volume
-- 
You are receiving this mail because:
You are on the CC list for the bug.
You are the assignee for the bug.


More information about the Bugs mailing list