Bug 1452194 - [gluster-block]:Create of gluster-block fails after setting the block profile because of data not getting sync
Summary: [gluster-block]:Create of gluster-block fails after setting the block profile...
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Gluster Storage
Classification: Red Hat Storage
Component: gluster-block
Version: rhgs-3.3
Hardware: Unspecified
OS: Unspecified
unspecified
urgent
Target Milestone: ---
: RHGS 3.3.0
Assignee: Prasanna Kumar Kalever
QA Contact: surabhi
URL:
Whiteboard:
Depends On:
Blocks: 1417151
TreeView+ depends on / blocked
 
Reported: 2017-05-18 14:03 UTC by surabhi
Modified: 2017-09-21 04:19 UTC (History)
5 users (show)

Fixed In Version: gluster-block-0.2-3.el7rhgs
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2017-09-21 04:19:33 UTC
Embargoed:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Product Errata RHEA-2017:2773 0 normal SHIPPED_LIVE new packages: gluster-block 2017-09-21 08:16:22 UTC

Description surabhi 2017-05-18 14:03:39 UTC
Description of problem:
****************************
If we set the virt profile options which is recommended by dev to resolve some issues the block create hangs and doesn't lists the blocks becaus ethe sync of data is not happening between gluster-block and below layers.


Version-Release number of selected component (if applicable):
gluster-block-0.2-1.x86_64
tcmu-runner-1.2.0-2.el7rhgs.x86_64

How reproducible:
Always

Steps to Reproduce:
1. Creat a gluster volume
2. Set the volume options as provided below
3. Create a gluster block

Actual results:
***************

gluster block fails to get created as the data is not getting synced between 
gluster-block and below layers


Expected results:
************************
gluster-block create should be successfull.


Volume info as follows:
***************************

Volume Name: blockstor
Type: Replicate
Volume ID: 7fcd2753-237c-432c-b855-20eb517be98b
Status: Started
Snapshot Count: 0
Number of Bricks: 1 x 3 = 3
Transport-type: tcp
Bricks:
Brick1: dhcp46-144.lab.eng.blr.redhat.com:/gluster/brick1
Brick2: dhcp46-151.lab.eng.blr.redhat.com:/gluster/brick1
Brick3: dhcp46-152.lab.eng.blr.redhat.com:/gluster/brick1
Options Reconfigured:
performance.strict-o-direct: on
performance.write-behind: off
user.cifs: off
features.shard: on
cluster.shd-wait-qlength: 10000
cluster.shd-max-threads: 8
cluster.locking-scheme: granular
cluster.data-self-heal-algorithm: full
cluster.server-quorum-type: server
cluster.quorum-type: auto
cluster.eager-lock: enable
network.remote-dio: enable
performance.low-prio-threads: 32
performance.stat-prefetch: off
performance.io-cache: off
performance.read-ahead: off
performance.quick-read: off
transport.address-family: inet
nfs.disable: on


Additional info:

As discussed and Prasanna debugged, this looks like an issue with data not getting synced because of the options set by virt profile + strict-o-direct on and write-behind off.

If we revert these options create works successfully.

Comment 4 Prasanna Kumar Kalever 2017-05-21 10:31:29 UTC
Related patch:
https://review.gluster.org/#/c/17340/

Comment 5 Prasanna Kumar Kalever 2017-05-21 10:31:46 UTC
Related patch:
https://review.gluster.org/#/c/17340/

Comment 9 surabhi 2017-06-19 12:47:44 UTC
Tried gluster-block create multiple times after turning features.shard to on , there are no issues seen with creates. Also tried multiple times delete and create of blocks with auth enable disable, turning vol options on and off, it works fine.
gluster-block create blockstor/goodblocks ha 2  10.70.46.152,10.70.46.144 1GiB
IQN: iqn.2016-12.org.gluster-block:34c61c12-8694-47b9-afef-e1e9250f16a5
PORTAL(S):  10.70.46.152:3260 10.70.46.144:3260
RESULT: SUCCESS
[root@dhcp46-152 ~]# gluster-block list
Inadequate arguments for list:
gluster-block list <volname> [--json*]
[root@dhcp46-152 ~]# gluster-block list blockstor
block1
bluff-block
block3
block6
block4
block10
goodblock
goodblocks


Moving the BZ to verified.
gluster-block-0.2.1-1.el7rhgs.x86_64
tcmu-runner-1.2.0-4.el7rhgs.x86_64

Comment 11 errata-xmlrpc 2017-09-21 04:19:33 UTC
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory, and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

https://access.redhat.com/errata/RHEA-2017:2773


Note You need to log in before you can comment on or make changes to this bug.