From: Ghislain Adnet <gadnet@aqueos.com>
To: linux-btrfs@vger.kernel.org
Subject: btrfd, is btrfs daemon a thing ?
Date: Wed, 24 Feb 2021 10:43:06 +0100 [thread overview]
Message-ID: <900f07e8-251f-de6f-1fcf-0168ca3ad72d@aqueos.com> (raw)
hi there,
As a newbie in Btrfs land i installed a raid1 configuration and played with it.
After hot removing a drive of the raid i got two remarks that i cannot find answer with with my google foo.
So, to not die stupid i post a little email here to see if there is solutions about this :)
The experiment finished well the raid was reconstructed ans some untouched partition were even recreated automaticaly when the drive was put back, this is very cool !
The one with changes had to be manualy replaced, that was espected.
The issues are:
- logs: my systemd journal and my kernel.log were completely stampeded by btrfs logs.
On the mdadm world you have some message about disapearing drives and then it stops.
On my test there was hundreds of megabytes of brtfs error logs.
- monitoring : on mdamd you have a daemon that can warn you and even automaticaly run programs to warn you of a failure.
I think zfs has this too with ZED.
I was not able to find such a thing in btrfs.
Does it exist such a monitoring system capable of warning the admin when error appear in btrfs other than cron grepping the logs or btrfs device stats ?
Is there anyway to mitigate the log issue and did someone took a shot at a monitoring system for btrfs ?
--
best regards,
Ghislain.
reply other threads:[~2021-02-24 9:52 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=900f07e8-251f-de6f-1fcf-0168ca3ad72d@aqueos.com \
--to=gadnet@aqueos.com \
--cc=linux-btrfs@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).