Bug 1359406

Summary: [RGW:NFS]:- Can't create object of size more than 256k from nfs mount point
Product: [Red Hat Storage] Red Hat Ceph Storage Reporter: shylesh <shmohan>
Component: RGWAssignee: Matt Benjamin (redhat) <mbenjamin>
Status: CLOSED ERRATA QA Contact: shylesh <shmohan>
Severity: high Docs Contact:
Priority: unspecified    
Version: 2.0CC: cbodley, ceph-eng-bugs, ceph-qe-bugs, hnallurv, kbader, kdreyer, kurs, mbenjamin, nlevine, owasserm, sweil, uboppana
Target Milestone: rcFlags: kurs: needinfo-
Target Release: 2.0   
Hardware: x86_64   
OS: Unspecified   
Whiteboard:
Fixed In Version: RHEL: ceph-10.2.2-36.el7cp Ubuntu: ceph_10.2.2-28redhat1xenial Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2016-08-23 19:45:03 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Attachments:
Description Flags
ganesha logs for this particular write op none

Description shylesh 2016-07-23 19:50:52 UTC
Created attachment 1183148 [details]
ganesha logs for this particular write op

Description of problem:
Trying to create an object of size greater than 256k is not possible from nfs mount point

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

ceph-radosgw-10.2.2-26.el7cp.x86_64
nfs-ganesha-rgw-2.3.2-2.el7cp.x86_64
nfs-ganesha-2.3.2-2.el7cp.x86_64

How reproducible:

always

Steps to Reproduce:
1. create a nfs-rgw setup with ganesh and mount .
2. try to create an object of size more than 256k 

dd if=/dev/urandom of=file bs=1M count=1
dd: error writing ‘file’: Input/output error
1+0 records in
0+0 records out
0 bytes (0 B) copied, 1.78552 s, 0.0 kB/s

-rw-rw-rw-. 1 root root 262144 Jul 23 19:27 file

from the output we can observer that only 256k is written.

 Attaching the logs

Comment 12 shylesh 2016-08-10 10:16:26 UTC
Verified on librgw2-10.2.2-38.el7cp.x86_64

Comment 15 errata-xmlrpc 2016-08-23 19:45:03 UTC
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.

https://rhn.redhat.com/errata/RHBA-2016-1755.html