Bug 762159 (GLUSTER-427) - flush on a file opened read-only should not hold locks
Summary: flush on a file opened read-only should not hold locks
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: GLUSTER-427
Product: GlusterFS
Classification: Community
Component: replicate
Version: mainline
Hardware: All
OS: Linux
low
medium
Target Milestone: ---
Assignee: Vikas Gorur
QA Contact:
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2009-12-02 19:31 UTC by Vikas Gorur
Modified: 2009-12-07 09:47 UTC (History)
1 user (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed:
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:

Attachments (Terms of Use)
Add an attachment (proposed patch, testcase, etc.)

Description Vikas Gorur 2009-12-02 19:31:54 UTC 
If no pre-op has been done an fd, there is no reason for the flush to
be a transaction. This will save some time for those files that have been
opened only for reading.
Comment 1 Anand Avati 2009-12-03 07:00:42 UTC 
PATCH: http://patches.gluster.com/patch/2506 in master (cluster/afr: Don't do transactional flush if pre-op has been nowhere done.)
Note You need to log in before you can comment on or make changes to this bug.