Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[Feature]: Filesystem differences/philosophies and metrics #16

Open
RincewindsHat opened this issue Jan 15, 2024 · 0 comments
Open

[Feature]: Filesystem differences/philosophies and metrics #16

RincewindsHat opened this issue Jan 15, 2024 · 0 comments
Labels
feature New feature or request

Comments

@RincewindsHat
Copy link
Member

Describe the feature request

It recently came to my attention, that a fixed number of inodes is only a characteristic of some file system, not all of them.
In this case it was btrfs which allocates inodes dynamically (and where the remaining space is more difficult to measure).
The general problem of different filesystem characteristics is far more extensive, there might be questions about the consistency of the journal or quotas instead of "physical" limits.
In general there are some things to consider for now and in the future:

  • There has to some filesystem-specific path for some measurements/tests
  • What can go wrong in a specific filesystem and should therefore be monitored?
@RincewindsHat RincewindsHat added feature New feature or request needs-triage Needs to be triaged labels Jan 15, 2024
@martialblog martialblog removed the needs-triage Needs to be triaged label Jan 15, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
feature New feature or request
Projects
None yet
Development

No branches or pull requests

2 participants