From: Marat Khalili <mkh@rqc.ru>
To: linux-btrfs <linux-btrfs@vger.kernel.org>
Subject: Re: notification about corrupt files from "btrfs scrub" in cron
Date: Thu, 23 Nov 2017 16:58:37 +0300 [thread overview]
Message-ID: <529fe690-b3c7-a63a-c574-4c4f443b4ba0@rqc.ru> (raw)
In-Reply-To: <CAMU1PDj+ovqRXOrcnRkr8rP4L+e=g9FXeTmaKBHQ-2o+r2+5vw@mail.gmail.com>
On 23/11/17 15:59, Mike Fleetwood wrote:
> Cron starts configured jobs at the scheduled time asynchronously.
> I.e. It doesn't block waiting for each command to finish. Cron notices
> when the job finishes and any output produced, written to stdout and/or
> stderr, by the job is emailed to the user. So no, a 2 hour job is not a
> problem for cron.
Minor additional advice -- prepend you command with:
> flock --nonblock /var/run/scrub.lock
to avoid running several scrubs simultaneously in case one takes more
than 24 hours to finish.
--
With Best Regards,
Marat Khalili
next prev parent reply other threads:[~2017-11-23 13:58 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-11-22 19:54 notification about corrupt files from "btrfs scrub" in cron ST
2017-11-23 9:41 ` Duncan
2017-11-23 11:47 ` ST
2017-11-23 12:59 ` Mike Fleetwood
2017-11-23 13:58 ` Marat Khalili [this message]
2017-11-24 1:04 ` Duncan
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=529fe690-b3c7-a63a-c574-4c4f443b4ba0@rqc.ru \
--to=mkh@rqc.ru \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.