Bug #40864
cephfs-shell: rmdir doesn't complain when directory is not empty
% Done:
0%
Source:
Community (dev)
Tags:
Backport:
nautilus
Regression:
No
Severity:
3 - minor
Reviewed:
Affected Versions:
ceph-qa-suite:
Component(FS):
cephfs-shell
Labels (FS):
task(easy)
Pull request ID:
Crash signature (v1):
Crash signature (v2):
Description
Passing rmdir an non-empty directory doesn't remove the directory, as it's expected. But not printing anything misleads the user into thinking that the directory might be deleted.
CephFS:~/>>> ls dir2/ CephFS:~/>>> ls dir2/ file1 CephFS:~/>>> rmdir dir2 CephFS:~/>>> ls dir2/ CephFS:~/>>> ls dir2 file1 CephFS:~/>>>
Related issues
History
#1 Updated by Rishabh Dave over 4 years ago
- Subject changed from rmdir: doesn't complain when directory is not empty to cephfs-shell: rmdir doesn't complain when directory is not empty
#2 Updated by Varsha Rao over 4 years ago
After this PR[https://github.com/ceph/ceph/pull/28514]
It does print an error message, but the message is not appropriate.
CephFS:~/>>> ls dir2/ CephFS:~/>>> ls dir2 file1 CephFS:~/>>> rmdir dir2 error: no such directory /dir2 exists
#3 Updated by Patrick Donnelly over 4 years ago
- Status changed from New to Pending Backport
- Target version set to v15.0.0
- Start date deleted (
07/22/2019) - Source set to Community (dev)
- Backport set to nautilus
- Pull request ID set to 30341
#4 Updated by Nathan Cutler over 4 years ago
- Copied to Backport #42157: nautilus: cephfs-shell: rmdir doesn't complain when directory is not empty added
#5 Updated by Nathan Cutler over 3 years ago
- Status changed from Pending Backport to Resolved
While running with --resolve-parent, the script "backport-create-issue" noticed that all backports of this issue are in status "Resolved" or "Rejected".