public inbox for util-linux@vger.kernel.org
 help / color / mirror / Atom feed
From: "Pádraig Brady" <P@draigBrady.com>
To: Frank Mayhar <fmayhar@google.com>
Cc: util-linux@vger.kernel.org
Subject: Re: [PATCH 0/4] Add functions to the fsck wrapper to improve standalone operation.
Date: Wed, 15 Feb 2012 14:00:18 +0000	[thread overview]
Message-ID: <4F3BBA72.90902@draigBrady.com> (raw)
In-Reply-To: <1328648733.11787.13.camel@peace.lax.corp.google.com>

On 02/07/2012 09:05 PM, Frank Mayhar wrote:
> This set of patches adds functions that help improve fsck operation in
> large installations and when running in unattended or headless mode.  It
> adds support for reporting rusage statistics for the individual fsck
> runs, for capturing fsck output, for killing fsck runs that take too
> long and for running scripts when each fsck completes.
> 
> We're currently using these functions to improve our fsck monitoring
> capability and to replace some unwieldy and hard-to-maintain shell
> scripts.

Couldn't you do this with separate fsck command runs,
and use standard system utils?

flist="/dev/sda1 /dev/sda2"
for sys in $flist; do
  timeout 10m fsck > /var/log/fsck.$(basename $sys) \
    && success_script $sys \
    || fail_script $sys
done

cheers,
Pádraig.

  reply	other threads:[~2012-02-15 14:10 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-02-07 21:05 [PATCH 0/4] Add functions to the fsck wrapper to improve standalone operation Frank Mayhar
2012-02-15 14:00 ` Pádraig Brady [this message]
2012-02-15 15:09   ` Frank Mayhar
2012-02-15 16:06     ` Pádraig Brady
2012-02-15 17:42       ` Karel Zak
2012-02-16 20:17         ` Frank Mayhar
2012-02-17  2:53           ` Pádraig Brady
2012-02-23 18:04             ` Frank Mayhar

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=4F3BBA72.90902@draigBrady.com \
    --to=p@draigbrady.com \
    --cc=fmayhar@google.com \
    --cc=util-linux@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