Bug 1432048 - Opening a file in RDRW mode when the quorum is not reached returns 0 instead of -1.
Summary: Opening a file in RDRW mode when the quorum is not reached returns 0 instead ...
Keywords:
Status: CLOSED WORKSFORME
Alias: None
Product: Red Hat Gluster Storage
Classification: Red Hat Storage
Component: glusterfs
Version: rhgs-3.3
Hardware: Unspecified
OS: Linux
low
medium
Target Milestone: ---
: ---
Assignee: Bug Updates Notification Mailing List
QA Contact: Bala Konda Reddy M
URL:
Whiteboard:
Depends On:
Blocks: 1355689
TreeView+ depends on / blocked
 
Reported: 2017-03-14 12:16 UTC by Ramakrishna Reddy Yekulla
Modified: 2019-05-29 08:43 UTC (History)
4 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2018-11-20 05:00:11 UTC
Embargoed:


Attachments (Terms of Use)

Description Ramakrishna Reddy Yekulla 2017-03-14 12:16:34 UTC
Description of problem:

While using a BlotDB in CNS-3.4+, the following has been observed that when the db file has been mounted on GlusterFS. 
 


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


How reproducible:


Steps to Reproduce:
1. 
2.
3.

Actual results:
open() with O_RDWR on a RO-filesystem returns 0 with NO ERROR. 
open() with O_RDWR on a RO file returns -1 with error == EACCESS


Expected results:
open() with O_RDWR on a RO-filesystem returns -1 with errno == EROFS
open() with O_RDWR on a RO file returns -1 with error == EACCESS


Additional info:

Comment 4 Amar Tumballi 2018-04-02 07:52:53 UTC
Can you test using 'gluster volume set <vol> open-behind disable' ?

If works, I recommend enabling that option for all volumes in CNS (if this is critical behavior). Else, will close with a known-issue.

Comment 6 Atin Mukherjee 2018-11-19 08:15:18 UTC
Is this behaviour seen in latest OCS releases?

Comment 7 Amar Tumballi 2018-11-20 05:00:11 UTC
Considering there was no update on bug other than the initial filing, and not reported by the QE during any of OCS/CNS testing, closing it as WORKSFORME. Please re-open if seen again.


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