Bug 1044356 - SMB:renaming a directory fails with error message directory not present when tried with the name of dir which had quota limit set
Summary: SMB:renaming a directory fails with error message directory not present when ...
Keywords:
Status: CLOSED WORKSFORME
Alias: None
Product: Red Hat Gluster Storage
Classification: Red Hat
Component: quota
Version: 2.1
Hardware: Unspecified
OS: Unspecified
high
unspecified
Target Milestone: ---
: ---
Assignee: Vijaikumar Mallikarjuna
QA Contact: surabhi
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2013-12-18 08:15 UTC by surabhi
Modified: 2016-09-17 12:39 UTC (History)
5 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2015-04-20 09:34:57 UTC
Target Upstream Version:


Attachments (Terms of Use)

Description surabhi 2013-12-18 08:15:04 UTC
Description of problem:
Renaming a directory with the name of another directory which was present on the mount point and had quota limit set and was deleted causes error and does not allow rename of the directory.

Version-Release number of selected component (if applicable):
glusterfs-fuse-3.4.0.49rhs-1.el6rhs.x86_64
glusterfs-server-3.4.0.49rhs-1.el6rhs.x86_64
samba-glusterfs-3.6.9-167.3.el6rhs.x86_64
glusterfs-3.4.0.49rhs-1.el6rhs.x86_64
glusterfs-debuginfo-3.4.0.49rhs-1.el6rhs.x86_64
glusterfs-geo-replication-3.4.0.49rhs-1.el6rhs.x86_64
glusterfs-api-devel-3.4.0.49rhs-1.el6rhs.x86_64
glusterfs-rdma-3.4.0.49rhs-1.el6rhs.x86_64
glusterfs-libs-3.4.0.49rhs-1.el6rhs.x86_64
glusterfs-api-3.4.0.49rhs-1.el6rhs.x86_64
glusterfs-devel-3.4.0.49rhs-1.el6rhs.x86_64


How reproducible:
seen only once

Steps to Reproduce:
1.Create directory A
2.Set quota on directory A 
3.Create directory B
4.Delete directory A and try to rename directory B as A

Actual results:
Got error message on windows client while renaming :saying directory A is not present cannot rename.

Expected results:
Rename should happen and there should not be such error.

Additional info:

Comment 2 Vijaikumar Mallikarjuna 2015-04-20 09:34:57 UTC
This is not reproducible. Please re-open if you see this issue again.


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