+++ This bug was initially created as a clone of Bug #842652 +++ Description of problem: Creating a directory and trying to rename it fails on stripe volume Version-Release number of selected component (if applicable): RHS 2.0.z How reproducible: Always Steps to Reproduce: 1. Create a stripe volume 2. mount the volume and create a directory say dir1 3. renamve the directory : mv dir1 dir2 Actual results: rename operation fails [root@nec-em13 mnt]# mv dir1 dir2 mv: cannot move `dir1' to a subdirectory of itself, `dir2' Expected results: Additional info: -07-24 06:32:52.121132] I [glusterfsd-mgmt.c:1565:mgmt_getspec_cbk] 0-glusterfs: No change in volfile, continuing [2012-07-24 06:32:52.124715] I [client-handshake.c:1636:select_server_supported_programs] 0-volset-client-0: Using Program GlusterFS 3.3.0, Num (1298437), Version (330) [2012-07-24 06:32:52.125201] I [client-handshake.c:1433:client_setvolume_cbk] 0-volset-client-0: Connected to 10.16.157.63:24011, attached to remote volume '/home/bricks/volset0'. [2012-07-24 06:32:52.125231] I [client-handshake.c:1445:client_setvolume_cbk] 0-volset-client-0: Server and Client lk-version numbers are not same, reopening the fds [2012-07-24 06:32:52.125537] I [client-handshake.c:453:client_set_lk_version_cbk] 0-volset-client-0: Server lk version = 1 [2012-07-24 06:34:02.342657] I [glusterfsd-mgmt.c:64:mgmt_cbk_spec] 0-mgmt: Volume file changed [2012-07-24 06:34:02.346265] I [glusterfsd-mgmt.c:1565:mgmt_getspec_cbk] 0-glusterfs: No change in volfile, continuing [2012-07-24 07:16:21.271285] W [fuse-bridge.c:1516:fuse_rename_cbk] 0-glusterfs-fuse: 71999: /dir1 -> /dir2 => -1 (Invalid argument) --- Additional comment from bfoster on 2012-07-24 09:11:28 EDT --- http://review.gluster.com/3720
verified on RHS2.0.z update 2. Now renaming works fine.
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. http://rhn.redhat.com/errata/RHBA-2012-1253.html