Bug #48318
Client: the directory's capacity will not be updated after write data into the directory
% Done:
0%
Source:
Community (dev)
Tags:
Backport:
octopus,nautilus
Regression:
No
Severity:
3 - minor
Reviewed:
Affected Versions:
ceph-qa-suite:
Component(FS):
Client
Labels (FS):
Pull request ID:
Crash signature (v1):
Crash signature (v2):
Description
The reproduction steps are as follows:
[root@ceph105 test]# mkdir dir1 [root@ceph105 test]# cd dir1/ [root@ceph105 dir1]# dd if=/dev/zero of=100M bs=100M count=1 1+0 records in 1+0 records out 104857600 bytes (105 MB) copied, 0.495317 s, 212 MB/s [root@ceph105 dir1]# cd .. [root@ceph105 test]# ll total 1 drwxr-xr-x. 2 root root 0 Nov 21 10:25 dir1 [root@ceph105 test]# ll total 1 drwxr-xr-x. 2 root root 0 Nov 21 10:25 dir1
Related issues
History
#1 Updated by Patrick Donnelly about 1 year ago
- Status changed from New to Won't Fix
rstats are propagated lazily. Try doing an fsync.
#2 Updated by Patrick Donnelly about 1 year ago
- Status changed from Won't Fix to Fix Under Review
- Assignee set to wei qiaomiao
- Target version set to v16.0.0
- Source set to Community (dev)
- Backport set to octopus,nautilus
- Pull request ID set to 38222
#3 Updated by Patrick Donnelly about 1 year ago
- Status changed from Fix Under Review to Pending Backport
#4 Updated by Backport Bot about 1 year ago
- Copied to Backport #48641: nautilus: Client: the directory's capacity will not be updated after write data into the directory added
#5 Updated by Backport Bot about 1 year ago
- Copied to Backport #48642: octopus: Client: the directory's capacity will not be updated after write data into the directory added
#6 Updated by Nathan Cutler 11 months 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".