All of lore.kernel.org
 help / color / mirror / Atom feed
From: Ed Tomlinson <edt@aei.ca>
To: linux-kernel@vger.kernel.org
Subject: Re: [PATCH] 2.6.0 - Watchdog patches (BK consistency checks)
Date: Tue, 30 Dec 2003 08:36:15 -0500	[thread overview]
Message-ID: <200312300836.16559.edt@aei.ca> (raw)
In-Reply-To: <20031230004907.GA29143@merlin.emma.line.org>

On December 29, 2003 07:49 pm, Matthias Andree wrote:
> Well, talk about FAAAAAAST drives (10,025/min SCSI kind) unless you have
> time to waste on all those BK consistency checks (which are, of course,
> what #3 is all about).
>
> Or am I missing some obvious short cut?

Is there a way to tell BK when to do consistency checks?  Here they easily take
15-20 min each time.  I would love to be able to tell BK to defer these checks.

Ed Tomlinson

  parent reply	other threads:[~2003-12-30 13:36 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-09-06 10:51 [PATCH] 2.6.0-test4 - Watchdog patches - Documentation Wim Van Sebroeck
2003-12-29 19:52 ` [PATCH] 2.6.0 - Watchdog patches Wim Van Sebroeck
2003-12-29 20:11   ` Linus Torvalds
2003-12-29 20:22     ` Wim Van Sebroeck
2003-12-29 20:30       ` Linus Torvalds
2003-12-30  0:49         ` Matthias Andree
2003-12-30  6:36           ` Linus Torvalds
2003-12-30 13:36           ` Ed Tomlinson [this message]
2003-12-30 19:13             ` [PATCH] 2.6.0 - Watchdog patches (BK consistency checks) Andy Isaacson
2003-12-30 19:56               ` Eric D. Mudama
2003-12-30 20:16                 ` Andy Isaacson
2003-12-31 16:33                   ` Ed Tomlinson
2003-12-31 15:01               ` Ed Tomlinson
2003-12-31 17:42                 ` Eric D. Mudama
2003-12-31 19:13                 ` Andy Isaacson
2003-12-29 20:36     ` [PATCH] 2.6.0 - Watchdog patches Jeff Garzik
2003-12-30 12:14       ` Paul Jackson

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=200312300836.16559.edt@aei.ca \
    --to=edt@aei.ca \
    --cc=linux-kernel@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.