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

Request: storage alerts for dom0 and domUs #4404

Closed
brendanhoar opened this issue Oct 18, 2018 · 2 comments
Closed

Request: storage alerts for dom0 and domUs #4404

brendanhoar opened this issue Oct 18, 2018 · 2 comments
Labels
R: duplicate Resolution: Another issue exists that is very similar to or subsumes this one.

Comments

@brendanhoar
Copy link

brendanhoar commented Oct 18, 2018

Qubes OS version:

R4.0

Affected component(s):

Storage subsystems.
System stability.


Steps to reproduce the behavior:

Run out of storage on a volume or pool in dom0 or a domU.

Expected behavior:

User would be alerted before this happens and can take action to avoid bad and sometimes irreversible outcomes.

Actual behavior:

User is surprised when entire system or a particular VM fails to work correctly and/or becomes corrupted and unusable.

General notes:

It may be useful to alert the user of storage issues before the (generally bad) effects of running out of storage occur. Probably best with configurable thresholds, e.g.: "predefined % remaining" or perhaps "total remaining storage". Monitoring could be broken down into two or three categories, all reported via a new widget (or updates to an existing one):

  1. Alerts for dom0 via widget: monitor dom0 volumes as well as any pools that Qubes utilizes for VM volume storage.

  2. Alerts for domU via widget utilizing Qubes Linux/windows tools: reported via RPC by the VM. Probably most critical for Linux and non-fullscreen Windows.

  3. Alerts for domU via widget without Qubes tools support: optional delayed-reporting scan after shutdown by temporarily attaching the VM's volumes to a newly-run dvm and performing a filesystem scan for mountable filesystems, then reported via RPC. Widget would be reporting on RPC data from dvm, but knows the original domU it was checking. OK, this one is probably a pipe dream. Probably best to create a script to do suggestion number 3.


Related issues:

@andrewdavidwong
Copy link
Member

Duplicate of #1872

@andrewdavidwong andrewdavidwong marked this as a duplicate of #1872 Oct 19, 2018
@andrewdavidwong
Copy link
Member

This appears to be a duplicate of an existing issue. If so, please comment on the appropriate existing issue instead. If you believe this is not really a duplicate, please leave a comment briefly explaining why. We'll be happy to take another look and, if appropriate, reopen this issue. Thank you.

@andrewdavidwong andrewdavidwong added the R: duplicate Resolution: Another issue exists that is very similar to or subsumes this one. label Oct 19, 2018
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
R: duplicate Resolution: Another issue exists that is very similar to or subsumes this one.
Projects
None yet
Development

No branches or pull requests

2 participants