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

start process to send email notifications upon btrfs problems? #88

Open
testbird opened this issue Oct 25, 2020 · 0 comments
Open

start process to send email notifications upon btrfs problems? #88

testbird opened this issue Oct 25, 2020 · 0 comments

Comments

@testbird
Copy link

testbird commented Oct 25, 2020

I am wondering how btrfs users can ensure to automatically get notified (only) upon errors and warnings (that usually happen in the background and are very likely to remain unnoticed).

Btrfsmaintenance seemed like good find for this, it covers the necessary background tasks.

But couldn't it also run something like a watchdog task (i.e. bash pipe)?
It could filter the log for any btrfs warnings and errors that may occur during the daily usage, and send out emails as soon as they occur.

ximion added a commit to ximion/btrfsmaintenance that referenced this issue Mar 19, 2022
This can be very useful for smaller setups where the admin still would
like to receive an email in case a disk in a btrfs RAID array fails.

Partially resolves kdave#88
ximion added a commit to ximion/btrfsmaintenance that referenced this issue Mar 19, 2022
This can be very useful for smaller setups where the admin still would
like to receive an email in case a disk in a btrfs RAID array fails.

Partially resolves kdave#88
ximion added a commit to ximion/btrfsmaintenance that referenced this issue Mar 21, 2022
This can be very useful for smaller setups where the admin still would
like to receive an email in case a disk in a btrfs RAID array fails.

Partially resolves kdave#88
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant