[Bug] Incorrect storage usage

[Zenderix]

Description of the bug

dash. is showing the wrong used storage in the dashboard.

df output shows the right used storage

it should be more like this, so a lot more than 2.5tb...

my docker compose volumes:

  volumes:
    - /etc/os-release:/etc/os-release:ro
    - /proc/1/ns/net:/mnt/host_ns_net:ro
    - /media:/mnt/host_media:ro
    - /storage:/mnt/host_storage
    - /storage/torrents:/mnt/host_torrents
    - /mnt:/mnt/host_mnt:ro
    - 

How to reproduce

No response

Relevant log output

No response

What browsers are you seeing the problem on?

No response

Where is your instance running?

Linux Server

Additional context

No response

[MauriceNino]

Hello, thank you for creating an issue! Is the df run inside the container, or outside? Because the mountpoints seem off to me.

[Zenderix]

It's run inside the container. I had some leftovers from trying out things in there, here is the current setup:

edit: I figured out that the shown storage should be about right for /storage & my root drive, however my LVM at /storage/torrents is not showing its used storage

[MauriceNino]

Can you please run the following command in your host and paste the output?

docker container exec -it dash. /bin/sh -c 'mkdir -p /test-storage && cd /test-storage && echo \'import * as si from "systeminformation";const run = async () => { const [disks, sizes] = await Promise.all([si.diskLayout(), si.fsSize()]); console.log("Disks", disks); console.log("Sizes", sizes);}; run();\' > index.js && echo \'{"name": "test-storage","version": "1.0.0","type": "module","description": "","main": "index.js","scripts": {},"author": "","license": "ISC","dependencies": {"systeminformation": "^5.11.16"}}\' > package.json && npm i && node .'

[Zenderix]

Can you please run the following command in your host and paste the output?

docker container exec -it dash. /bin/sh -c 'mkdir -p /test-storage && cd /test-storage && echo \'import * as si from "systeminformation";const run = async () => { const [disks, sizes] = await Promise.all([si.diskLayout(), si.fsSize()]); console.log("Disks", disks); console.log("Sizes", sizes);}; run();\' > index.js && echo \'{"name": "test-storage","version": "1.0.0","type": "module","description": "","main": "index.js","scripts": {},"author": "","license": "ISC","dependencies": {"systeminformation": "^5.11.16"}}\' > package.json && npm i && node .'

-bash: syntax error near unexpected token `('

[MauriceNino]

Doesn't work on bash as it seems...

Try this instead:

docker container exec -it dash. /bin/sh -c 'git clone https://github.com/MauriceNino/disk-info /disk-info && cd /disk-info && npm i && node .'

[Zenderix]

Doesn't work on bash as it seems...

Try this instead:

docker container exec -it dash. /bin/sh -c 'git clone https://github.com/MauriceNino/disk-info /disk-info && cd /disk-info && npm i && node .'

/bin/sh: git: not found

ungute gschicht xD

[MauriceNino]

damn git is already installed in the dev version - last try haha:

docker container exec -it dashdot_dev_dash_1 /bin/sh -c 'apk add git && git clone https://github.com/MauriceNino/disk-info /disk-info && cd /disk-info && npm i && node .'

[Zenderix]

damn git is already installed in the dev version - last try haha:

docker container exec -it dashdot_dev_dash_1 /bin/sh -c 'apk add git && git clone https://github.com/MauriceNino/disk-info /disk-info && cd /disk-info && npm i && node .'

Disks [
{
device: '/dev/sda',
type: 'HD',
name: 'ST1000LM024 HN-M',
vendor: 'Seagate',
size: 1000204886016,
bytesPerSector: null,
totalCylinders: null,
totalHeads: null,
totalSectors: null,
totalTracks: null,
tracksPerCylinder: null,
sectorsPerTrack: null,
firmwareRevision: '0001',
serialNum: '',
interfaceType: 'SATA',
smartStatus: 'unknown',
temperature: null
},
{
device: '/dev/sdb',
type: 'HD',
name: 'EARS-00Y5B1 ',
vendor: 'WDC WD10',
size: 1000204886016,
bytesPerSector: null,
totalCylinders: null,
totalHeads: null,
totalSectors: null,
totalTracks: null,
tracksPerCylinder: null,
sectorsPerTrack: null,
firmwareRevision: '0327',
serialNum: '',
interfaceType: 'USB',
smartStatus: 'unknown',
temperature: null
},
{
device: '/dev/sdc',
type: 'HD',
name: 'EZEX-08WN4A0 ',
vendor: 'WDC WD10',
size: 1000204886016,
bytesPerSector: null,
totalCylinders: null,
totalHeads: null,
totalSectors: null,
totalTracks: null,
tracksPerCylinder: null,
sectorsPerTrack: null,
firmwareRevision: '0327',
serialNum: '',
interfaceType: 'USB',
smartStatus: 'unknown',
temperature: null
},
{
device: '/dev/sdd',
type: 'HD',
name: '000-1H4168 ',
vendor: 'ST4000VN',
size: 4000787030016,
bytesPerSector: null,
totalCylinders: null,
totalHeads: null,
totalSectors: null,
totalTracks: null,
tracksPerCylinder: null,
sectorsPerTrack: null,
firmwareRevision: '0327',
serialNum: '',
interfaceType: 'USB',
smartStatus: 'unknown',
temperature: null
}
]
Sizes [
{
fs: 'overlay',
type: 'overlay',
size: 527295578112,
used: 44320841728,
available: 456114413568,
use: 8.86,
mount: '/'
},
{
fs: '/dev/sda2',
type: 'ext4',
size: 527295578112,
used: 44320841728,
available: 456114413568,
use: 8.86,
mount: '/mnt/host_media'
},
{
fs: '/dev/sdd1',
type: 'ext4',
size: 3936818806784,
used: 2702606073856,
available: 1034156703744,
use: 72.32,
mount: '/mnt/host_storage'
},
{
fs: '/dev/mapper/torrents-torrents',
type: 'ext4',
size: 1967854387200,
used: 1662309072896,
available: 205508231168,
use: 89,
mount: '/mnt/host_storage/torrents'
}
]

wouldn't be any fun if it was easy :P

[MauriceNino]

Can you try pulling the latest dev image and running that instead of prod? (docker image pull mauricenino/dashdot:dev)

[Zenderix]

Can you try pulling the latest dev image and running that instead of prod? (docker image pull mauricenino/dashdot:dev)

seems to work perfectly now!

Besten Dank!

[MauriceNino]

Kein Problem ;)

New main release will be published tomorrow, if you want to switch back from dev, btw.

[Zenderix]

Kein Problem ;)

New main release will be published tomorrow, if you want to switch back from dev, btw.

If I don't forget I'll change back tomorrow.

Sent something your way, danke nochmals aus der Steiermark :)

[MauriceNino]

Thank you, much appreciated :)

[MauriceNino]

🎉 This issue has been resolved in version 3.2.0

Please check the changelog for more details.