Bug 1339145 - "No such file of directory" error on deleting the nested directory structure.
Summary: "No such file of directory" error on deleting the nested directory structure.
Alias: None
Product: GlusterFS
Classification: Community
Component: posix
Version: mainline
Hardware: All
OS: All
Target Milestone: ---
Assignee: Pranith Kumar K
QA Contact:
Depends On:
TreeView+ depends on / blocked
Reported: 2016-05-24 08:54 UTC by Karan Sandha
Modified: 2019-05-09 10:15 UTC (History)
6 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Last Closed: 2019-05-09 10:15:14 UTC
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:

Attachments (Terms of Use)

Description Karan Sandha 2016-05-24 08:54:39 UTC
Description of problem:
Nested directory name leads to no such file or directory. basically if we create nested directory and delete the directory from the mount point when one if the brick is down. it leads to error and warnings.

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

logs placed in the repo @ rhsqe-repo.lab.eng.blr.redhat.com:/var/www/html/sosreports/<bug>
How reproducible: 2/2

Steps to Reproduce:
1. create a nested directory using below script:-
[root@dhcp42-93 nfs]# cat dd.sh 
for ((i=1; i<=1000; i++))
mkdir -pv directory$i
cd directory$i
dd if=/dev/urandom of=file$i bs=1k count=1 status=progress

2.kill one of the bricks
3.rm -rf directory* from the mount point using FUSE
4 bring back the brick and check brick logs for the failed directory structure.

Actual results:
Errors were observed on the logs and unable to delete the files.

Expected results:
Files and directory should be deleted from the brick too.

Additional info:
Master build 3.9 dev

Comment 1 Amar Tumballi 2019-05-09 10:15:14 UTC
We are not picking this issue in upcoming releases, and hence marking as DEFERRED. Will revisit after couple of releases depending on time/resource.

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