Project

General

Profile

Actions
Copy link

Bug #48318

closed

Client: the directory's capacity will not be updated after write data into the directory

Added by wei qiaomiao over 5 years ago. Updated 8 months ago.

Status:
Resolved
Priority:
Normal
Assignee:
wei qiaomiao
Category:
-
Target version:
Ceph - v16.0.0
% Done:

0%

Source:
Community (dev)
Backport:
octopus,nautilus
Regression:
No
Severity:
3 - minor
Reviewed:
Affected Versions:
ceph-qa-suite:
Component(FS):
Client
Labels (FS):
Pull request ID:
38222
Tags (freeform):
Merge Commit:
7830534a0e4826c07ef4ebca8668272236423148
Fixed In:
v16.0.0-8392-g7830534a0e
Released In:
v16.2.0~481
Upkeep Timestamp:
2025-07-14T19:23:35+00:00

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 2 (0 open — 2 closed)

Copied to CephFS - Backport #48641: nautilus: Client: the directory's capacity will not be updated after write data into the directoryResolvedWei-Chung ChengActions
Copied to CephFS - Backport #48642: octopus: Client: the directory's capacity will not be updated after write data into the directoryResolvedWei-Chung ChengActions
Actions
Copy link
 #1

Updated by Patrick Donnelly over 5 years ago

  • Status changed from New to Won't Fix

rstats are propagated lazily. Try doing an fsync.

Actions
Copy link
 #2

Updated by Patrick Donnelly over 5 years 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
Actions
Copy link
 #3

Updated by Patrick Donnelly over 5 years ago

  • Status changed from Fix Under Review to Pending Backport
Actions
Copy link
 #4

Updated by Upkeep Bot over 5 years ago

  • Copied to Backport #48641: nautilus: Client: the directory's capacity will not be updated after write data into the directory added
Actions
Copy link
 #5

Updated by Upkeep Bot over 5 years ago

  • Copied to Backport #48642: octopus: Client: the directory's capacity will not be updated after write data into the directory added
Actions
Copy link
 #6

Updated by Nathan Cutler about 5 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".

Actions
Copy link
 #7

Updated by Upkeep Bot 8 months ago

  • Merge Commit set to 7830534a0e4826c07ef4ebca8668272236423148
  • Fixed In set to v16.0.0-8392-g7830534a0e
  • Released In set to v16.2.0~481
  • Upkeep Timestamp set to 2025-07-14T19:23:35+00:00
Actions
Copy link

Also available in: Atom PDF