Skip to content

GitLab

  • Projects
  • Groups
  • Snippets
  • Help
    • Loading...
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in
gparted
gparted
  • Project overview
    • Project overview
    • Details
    • Activity
    • Releases
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
  • Issues 33
    • Issues 33
    • List
    • Boards
    • Labels
    • Service Desk
    • Milestones
  • Merge Requests 6
    • Merge Requests 6
  • CI/CD
    • CI/CD
    • Pipelines
    • Jobs
    • Schedules
  • Operations
    • Operations
    • Incidents
    • Environments
  • Packages & Registries
    • Packages & Registries
    • Container Registry
  • Analytics
    • Analytics
    • CI/CD
    • Repository
    • Value Stream
  • Wiki
    • Wiki
  • Snippets
    • Snippets
  • Members
    • Members
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
Collapse sidebar
  • GNOME
  • gpartedgparted
  • Merge Requests
  • !50

Merged
Created Nov 09, 2019 by Mike Fleetwood@mfleetwoMaintainer

Calculate JFS size accurately

  • Overview 6
  • Commits 4
  • Pipelines 5
  • Changes 3

JFS was one of the file systems which was considered to have intrinsic unallocated space (reported size of the file system doesn't match the size of the partition). Commit 7ebedc4b "Don't show intrinsic unallocated space (#499202)". Both when using jfs-utils for unmounted and statvfs() when mounted.

Recent commit c15d0cd6 "Accept FS usage figures within significant unallocated threshold (!49 (merged))" peeked my interest. So I've read the mkfs.jfs source code and worked out how to accurately query and calculate the size of a JFS. This patchset is the result.

Edited Nov 10, 2019 by Mike Fleetwood
Assignee
Assign to
Reviewer
Request review from
None
Milestone
None
Assign milestone
Time tracking
Source branch: jfs-usage