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

Raid health check #47

Open
ldrrp opened this issue Jul 21, 2022 · 0 comments
Open

Raid health check #47

ldrrp opened this issue Jul 21, 2022 · 0 comments
Labels
enhancement New feature or request
Milestone

Comments

@ldrrp
Copy link
Contributor

ldrrp commented Jul 21, 2022

Problem

Currently there are no checks for raid health. This is a problem if we want to ensure data is not lost.

Solution

On a cron check for the health of the raids and if any are unhealthy we should notify the user and log the issue.

  • We must scan for all mdadm drives.
  • We should add those drives to a list of raids to configure in config.yml.
  • Include config.yml settings disk checks with a custom golang struct.
  • We will need a new model for system commands.

Example:

 - raid:
    - uuid: AISDYIAYSIDYUA
      options:
        - notification:
            enabled: true
        - log: true
    - uuid: BISDASDSAJFYUA
      options:
        - notification:
            enabled: true
        - log: true

Notify may be "true", "false" or "email" etc. Parsed as string. True will use server default.

Additionally we should allow the user to call the raid check directly.

Steps to Reproduce the Problem

  1. ./server.bin -system raid-check
@ldrrp ldrrp added this to the v3.1 milestone Jul 21, 2022
@ldrrp ldrrp added the enhancement New feature or request label Jul 21, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
None yet
Development

No branches or pull requests

1 participant