-
Notifications
You must be signed in to change notification settings - Fork 22
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
Disk graph doesn't show usage for LVM, LUKS, etc (patch available) #57
Comments
@loftyhauser do you still have the patch handy? I'd be happy to help you get it on github if you'd like. I'm having the same problem -- only the /boot partition can be monitored. I was hoping that monitoring entire drives, rather than partitions, would work, but no such luck. |
On my fork here https://github.com/loftyhauser/multiload-ng. |
Thanks! It works great for me. |
Hmm, I spoke too soon. With this patch, my MATE multiload applet crashes like clockwork every 15 minutes. The crash is always in the same place, which is in the CPU usage monitor and therefore unrelated to the actually modified code:
|
Yep, that was it. You also forgot to free the buffer, leading to a memory leak. Both are fixed here. (edit: fixed broken link) Thanks again for this patch! |
Ah, glad you caught the error! I noticed that the applet crashed regularly, but since XFCE automatically restarted the app, it didn't make much difference (it was annoying though). |
My NVMe disk is also not showing up in multiload-ng even with your patches applied. It's devpath is Thanks! |
Thanks @ndorf that is indeed the fix for NVMe drives. However it doesn't seem to be compatible with the patchset here. I guess I'll stick with the NVME patches for now. |
@haarp d'oh, you might want to try nylen's fork at https://github.com/nylen/multiload-ng |
Nice, that fork has everything I need, thanks! |
The disk graph doesn't show any disk usage for partitions that are not directly mounted, and so it doesn't show usage for partitions that are used by LVM or LUKS, for example. When getting the data, instead of looping through the mounted partitions, perhaps you can simply loop through the block devices as you do to populate the filter. I've implemented the change and have a patch to contribute (as soon as I figure out how to use GitHub!).
The text was updated successfully, but these errors were encountered: