Bug 1470955

Summary:	Add a check to disallow block creation when size of block device is less than 1 sector i.e., 512 bytes
Product:	[Red Hat Storage] Red Hat Gluster Storage	Reporter:	krishnaram Karthick <kramdoss>
Component:	gluster-block	Assignee:	Prasanna Kumar Kalever <prasanna.kalever>
Status:	CLOSED ERRATA	QA Contact:	Sweta Anandpara <sanandpa>
Severity:	medium	Docs Contact:
Priority:	unspecified
Version:	cns-3.9	CC:	rcyriac, rhs-bugs
Target Milestone:	---
Target Release:	CNS 3.10
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:	gluster-block-0.2.1-14.1.el7rhgs	Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:
Clones:	1545102 (view as bug list)		Environment:
Last Closed:	2018-09-12 09:25:17 UTC	Type:	Bug
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:
Bug Depends On:	1595176
Bug Blocks:	1545102, 1568861

Description krishnaram Karthick 2017-07-14 06:49:24 UTC

Description of problem:
Any block device created with size which is less than 512 bytes doesn't get detected as an iscsi target. Hence, a block device created of size less than 512 bytes should be disallowed.

rpm -qa | grep 'gluster'
glusterfs-server-3.8.4-32.el7rhgs.x86_64
gluster-block-0.2.1-4.el7rhgs.x86_64
glusterfs-libs-3.8.4-32.el7rhgs.x86_64
glusterfs-3.8.4-32.el7rhgs.x86_64
glusterfs-api-3.8.4-32.el7rhgs.x86_64
glusterfs-cli-3.8.4-32.el7rhgs.x86_64
glusterfs-fuse-3.8.4-32.el7rhgs.x86_64
glusterfs-geo-replication-3.8.4-32.el7rhgs.x86_64
glusterfs-client-xlators-3.8.4-32.el7rhgs.x86_64

How reproducible:
Always

Steps to Reproduce:
1. create a block device less than 512 bytes

Actual results:
block device doesn't get created

Expected results:
disallow block device creation of size < 512 bytes

Additional info:

Comment 2 Prasanna Kumar Kalever 2017-07-14 07:23:02 UTC

Patch:
https://review.gluster.org/#/c/17747/

Comment 9 errata-xmlrpc 2018-09-12 09:25:17 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-2018:2691