From: Rich Rauenzahn <rich@shroop.net>
To: crocket <crockabiscuit@gmail.com>, linux-btrfs@vger.kernel.org
Subject: Re: How do I make 'btrfs scrub' report errors via email?
Date: Sat, 13 Jun 2015 21:34:15 -0700 [thread overview]
Message-ID: <557D0447.6040506@shroop.net> (raw)
In-Reply-To: <CAL0=0H19M7JG4o4p55Li3tF4PeA-UXb8mURcSOdPLwxfL0c1DQ@mail.gmail.com>
On 6/13/2015 6:48 AM, crocket wrote:
> I can check the result of 'btrfs scrub' later, but I don't want to
> take time to actually check it.
> Does anyone know how to make 'btrfs scrub' report errors via email?
> It seems google doesn't know.
I use this job in /etc/cron.d/btrfs.scrub.cron :
0 0 * * fri root for dev in `mount | grep "type btrfs" | awk '{print
$1}' | sort -u`; do echo --------------------------; echo Scrubbing
$dev :; echo --------------------------; /usr/sbin/btrfs scrub start -B
$dev; done
I also use sec:
http://superuser.com/questions/789303/how-to-monitor-btrfs-filesystem-raid-for-errors
next prev parent reply other threads:[~2015-06-14 4:34 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-06-13 13:48 How do I make 'btrfs scrub' report errors via email? crocket
2015-06-14 3:56 ` Duncan
2015-06-14 4:34 ` Rich Rauenzahn [this message]
2015-06-17 17:48 ` Marc MERLIN
[not found] ` <CAL0=0H0OtLOY0toMcLGtmj1s1TywuO2MDmfOcpR2vNzp_czoQQ@mail.gmail.com>
2015-06-18 1:23 ` Marc MERLIN
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=557D0447.6040506@shroop.net \
--to=rich@shroop.net \
--cc=crockabiscuit@gmail.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