Bug 1420328 – nfs clients see EIO/IO error when same file is copied from 2 different clients to the same mountpoint

Bugzilla will be upgraded to version 5.0. The upgrade date is tentatively scheduled for 2 December 2018, pending final testing and feedback.

Bug 1420328 - nfs clients see EIO/IO error when same file is copied from 2 different clients to the same mountpoint

Summary:	nfs clients see EIO/IO error when same file is copied from 2 different client...

Status:	CLOSED NOTABUG

Aliases:	None

Product:	Red Hat Ceph Storage
Classification:	Red Hat
Component:	RGW (Show other bugs)
Sub Component:
Version:	2.2
Hardware:	Unspecified Unspecified

Priority	unspecified Severity unspecified
Target Milestone:	rc
Target Release:	3.1
Assigned To:	Matt Benjamin (redhat)
QA Contact:	Ramakrishnan Periyasamy
Docs Contact:	Bara Ancincova

URL:
Whiteboard:
Keywords:

Depends On:	1418201
Blocks:	1437916
	Show dependency tree / graph

Reported:	2017-02-08 08:14 EST by Hemanth Kumar
Modified:	2017-10-24 08:38 EDT (History)
CC List:	11 users (show)

See Also:
Fixed In Version:
Doc Type:	Known Issue
Doc Text:	.Simultaneous upload operations to the same file cause I/O errors Simultaneous upload operations to the same file location by different NFS clients cause I/O errors on both clients. Consequently, no data is updated in the Ceph Object Gateway cluster; if an object already existed in the cluster in the same location, it is unchanged. To work around this problem, do not simultaneously upload to the same file location.
Story Points:	---
Clone Of:	1418201
Environment:
Last Closed:	2017-07-06 11:07:34 EDT
Type:	Bug
Regression:	---
Mount Type:	---
Documentation:	---
CRM:
Verified Versions:
Category:	---
oVirt Team:	---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---

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

Groups: None (edit)

Comment 3 Matt Benjamin (redhat) 2017-02-08 09:20:54 EST

Also updating the bug title, this is NOT a crash bug.

Comment 10 Ken Dreyer (Red Hat) 2017-04-25 20:42:17 EDT

If this is something we will never change, CLOSED WONTFIX is appropriate.

Comment 11 Matt Benjamin (redhat) 2017-04-25 21:03:06 EDT

(In reply to Ken Dreyer (Red Hat) from comment #10)
> If this is something we will never change, CLOSED WONTFIX is appropriate.

I think this behavior will one day change, but not in 2.3 and likely not 3.0.  It seems like the doc/note should carry forward.

Comment 12 Ken Dreyer (Red Hat) 2017-04-25 21:06:55 EDT

Ok, blocking the 2.3 release notes bug, in that case.

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