Bug 828681 - Document for default buffere mode of fileio is incorrect.
Document for default buffere mode of fileio is incorrect.
Product: Red Hat Enterprise Linux 6
Classification: Red Hat
Component: fcoe-target-utils (Show other bugs)
All Linux
low Severity low
: rc
: ---
Assigned To: Andy Grover
Petr Beňas
Depends On: 846670
  Show dependency treegraph
Reported: 2012-06-05 03:57 EDT by Gris Ge
Modified: 2015-01-04 18:02 EST (History)
2 users (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2013-02-21 05:48:49 EST
Type: Bug
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)

  None (edit)
Description Gris Ge 2012-06-05 03:57:58 EDT
Description of problem:

"targetcli /backstores/fileio/ help create" said:
The buffered parameter is a boolean stating whether or not to enable buffered mode. It is disabled by default (synchronous mode).

But this how creating LUN output:
/backstores/fileio> /backstores/fileio create disk2 /tmp/fcoe-lun2 10G
Using buffered mode.
Created fileio disk2 with size 10G
Entering new node /backstores/fileio/disk2

Apparently, the default value is "enable buffer".

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

How reproducible:

Steps to Reproduce:
Actual results:

Expected results:

Additional info:
Comment 2 Andy Grover 2012-08-08 15:09:25 EDT
buffered mode got replaced by write_back setting. Default setting for write_back should be documented correctly, i.e. on by default.
Comment 4 Petr Beňas 2012-10-17 08:32:20 EDT
Reproduced in fcoe-target-utils-2.0rc1.fb10-5.el6.noarch and verified in fcoe-target-utils-2.0rc1.fb16-1.el6.noarch.
Comment 6 errata-xmlrpc 2013-02-21 05:48:49 EST
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.


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