Bugzilla will be upgraded to version 5.0. The upgrade date is tentatively scheduled for 2 December 2018, pending final testing and feedback.
Bug 1450274 - Move fails on NFS-Ganesha-RGW for nfs version v3.
Move fails on NFS-Ganesha-RGW for nfs version v3.
Status: CLOSED ERRATA
Product: Red Hat Ceph Storage
Classification: Red Hat
Component: RGW (Show other bugs)
2.3
Unspecified Unspecified
unspecified Severity unspecified
: rc
: 2.3
Assigned To: Matt Benjamin (redhat)
rakesh
:
Depends On:
Blocks:
  Show dependency treegraph
 
Reported: 2017-05-12 02:32 EDT by rakesh
Modified: 2017-07-30 11:56 EDT (History)
8 users (show)

See Also:
Fixed In Version: RHEL: ceph-10.2.7-18.el7cp Ubuntu: ceph_10.2.7-20redhat1
Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed: 2017-06-19 09:33:14 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)


External Trackers
Tracker ID Priority Status Summary Last Updated
Ceph Project Bug Tracker 19932 None None None 2017-05-15 17:39 EDT
Red Hat Product Errata RHBA-2017:1497 normal SHIPPED_LIVE Red Hat Ceph Storage 2.3 bug fix and enhancement update 2017-06-19 13:24:11 EDT

  None (edit)
Description rakesh 2017-05-12 02:32:50 EDT
Description of problem:

When trying to move a file on a nfs mount, the move of this file fails. know that the file is created in a base directory(which is a bucket). for ex: 

the mount point is : /mnt/ganesha-mount/

the path of the file is /mnt/ganesha-mount/base_dir0/file0

now when tried to move the file to a different name:

mv file0 file1

i see the following error: 

mv: cannot move ‘file0’ to ‘file1’: Operation not permitted. 

the same happens even using with sudo.
Comment 10 errata-xmlrpc 2017-06-19 09:33:14 EDT
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://access.redhat.com/errata/RHBA-2017:1497

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