Project

General

Profile

Bug #56414

mounting subvolume shows size/used bytes for entire fs, not subvolume

Added by Xiubo Li 5 months ago. Updated 3 months ago.

Status:
Resolved
Priority:
Normal
Assignee:
Category:
-
Target version:
-
% Done:

0%

Source:
Tags:
Backport:
Regression:
No
Severity:
3 - minor
Reviewed:
Affected Versions:
ceph-qa-suite:
Component(FS):
libcephfs
Labels (FS):
quotas
Pull request ID:
Crash signature (v1):
Crash signature (v2):

Description

When mounting a subvolume at the base dir of the subvolume, the kernel client correctly shows the size/usage of a subvol:

Filesystem                                                                                            Size  Used Avail Use% Mounted on
xxx:6789:/volumes/_nogroup/4db8f9a6-926b-4306-8a6d-0e1b897c1d2f/d2ef5fea-040c-4ec1-b1bb-66073f9fc8ac  8.8T     0  8.8T   0% /cephfs

However if the client mounts a subdir of the subvolume, they see the size/usage of the entire cephfs:

Filesystem                                                                                                      Size  Used Avail Use% Mounted on
xxx:6789:/volumes/_nogroup/4db8f9a6-926b-4306-8a6d-0e1b897c1d2f/d2ef5fea-040c-4ec1-b1bb-66073f9fc8ac/my/subdir  1.3P  430T  860T  34% /var/lib/service

`ceph-fuse` does not have this behaviour -- mounting at a subdir below the subvolume shows the "correct" subvolume size and usage.


Related issues

Copied from Linux kernel client - Bug #55090: mounting subvolume shows size/used bytes for entire fs, not subvolume New

History

#1 Updated by Xiubo Li 5 months ago

  • Copied from Bug #55090: mounting subvolume shows size/used bytes for entire fs, not subvolume added

#2 Updated by Xiubo Li 5 months ago

  • Status changed from New to In Progress

Hit the same issue in libcephfs.

#3 Updated by Xiubo Li 5 months ago

  • Status changed from In Progress to Fix Under Review
  • Pull request ID set to 46867

#4 Updated by Xiubo Li 5 months ago

  • Pull request ID changed from 46867 to 46902

#5 Updated by Rishabh Dave 3 months ago

  • Status changed from Fix Under Review to Resolved

Also available in: Atom PDF