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

FIX: InfluxDB NSM Disk Usage visualization #10520

Closed
dougburks opened this issue Jun 6, 2023 · 1 comment · Fixed by #10559
Closed

FIX: InfluxDB NSM Disk Usage visualization #10520

dougburks opened this issue Jun 6, 2023 · 1 comment · Fixed by #10559
Assignees
Labels
2.4 Planned for 2.4.X

Comments

@dougburks
Copy link
Contributor

dougburks commented Jun 6, 2023

Reported at #10501 (reply in thread) and duplicated on a fresh 2.4.2 installation.

@dougburks dougburks added the 2.4 Planned for 2.4.X label Jun 6, 2023
@jertel jertel linked a pull request Jun 9, 2023 that will close this issue
@jertel jertel self-assigned this Jun 9, 2023
@jertel
Copy link
Contributor

jertel commented Jun 9, 2023

Validation of fix follows.

This is from an ISO install:
image

correlates with df:

[onion@securityonion ~]$ df -h
Filesystem               Size  Used Avail Use% Mounted on
devtmpfs                 4.0M     0  4.0M   0% /dev
tmpfs                    7.7G   20K  7.7G   1% /dev/shm
tmpfs                    3.1G   11M  3.1G   1% /run
/dev/mapper/system-root   83G   21G   63G  25% /
/dev/mapper/system-nsm   173G   11G  163G   6% /nsm
/dev/sda2                507M  211M  297M  42% /boot
tmpfs                    1.6G     0  1.6G   0% /run/user/1000
tmpfs                    1.6G     0  1.6G   0% /run/user/0
tmpfs                    1.6G     0  1.6G   0% /run/user/939

@jertel jertel closed this as completed Jun 9, 2023
@github-actions github-actions bot locked as resolved and limited conversation to collaborators Feb 25, 2024
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
2.4 Planned for 2.4.X
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants