Bug 146721

Summary:	iscsi software initiator should set vary_io in Scsi_Host_Template
Product:	Red Hat Enterprise Linux 3	Reporter:	Dave Wysochanski <davidw>
Component:	iscsi-initiator-utils	Assignee:	Tom Coughlan <coughlan>
Status:	CLOSED WONTFIX	QA Contact:	Brock Organ <borgan>
Severity:	medium	Docs Contact:
Priority:	medium
Version:	3.0	CC:	157070.alewis, coughlan, davidw, shillman
Target Milestone:	---
Target Release:	---
Hardware:	All
OS:	Linux
Whiteboard:
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2007-10-19 19:08:05 UTC	Type:	---
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:

Description Dave Wysochanski 2005-02-01 00:11:22 UTC

Description of problem: 
The iSCSI software initiator should set vary_io in the
Scsi_Host_Template so that sector sized direct IO can be done.
There's no underlying limitation to this, since this is iSCSI, so it
should set this flag.


Version-Release number of selected component (if applicable):
- iscsi driver in kernel 2.4.21-27.ELsmp (3.6.1 iscsi driver module)

How reproducible:
- Happens any time you want to do sector sized IO with a file or
device opened with O_DIRECT

Steps to Reproduce:
1. open a file with O_DIRECT flag
2. try to read/write with sector sized IO
  
Actual results:
- Error if you try to use sector sized IO after opening a file with
O_DIRECT.

Expected results:
- No error

Additional info:

Comment 1 Suzanne Hillman 2005-02-07 17:34:29 UTC

Internal RFE bug #147366 entered; will be considered for future releases.

Comment 2 Tom Coughlan 2005-03-08 16:37:50 UTC

Unfortunately, this did not get in to U5. I am reluctant to change anything
until BZ 145818 is fixed anyway. 

Dave, did you observe that setting vary_io actually fixed the O_DIRECT sector
sized IO problem? I would not have expected that.

Comment 3 RHEL Program Management 2007-10-19 19:08:05 UTC

This bug is filed against RHEL 3, which is in maintenance phase.
During the maintenance phase, only security errata and select mission
critical bug fixes will be released for enterprise products. Since
this bug does not meet that criteria, it is now being closed.
 
For more information of the RHEL errata support policy, please visit:
http://www.redhat.com/security/updates/errata/
 
If you feel this bug is indeed mission critical, please contact your
support representative. You may be asked to provide detailed
information on how this bug is affecting you.