linux-ext4.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Andreas Dilger <adilger@sun.com>
To: Adrian Hunter <adrian.hunter@nokia.com>
Cc: akpm@linux-foundation.org, linux-ext4@vger.kernel.org,
	Artem Bityutskiy <artem.bityutskiy@nokia.com>
Subject: Re: [PATCH 1/2] HACK: ext3: mount fast even when recovering
Date: Tue, 14 Jul 2009 17:22:21 -0400	[thread overview]
Message-ID: <20090714212221.GD4829@webber.adilger.int> (raw)
In-Reply-To: <20090714140301.25993.97749.sendpatchset@ahunter-tower>

On Jul 14, 2009  17:03 +0300, Adrian Hunter wrote:
> Speed up ext3 recovery mount time by not sync'ing the
> block device.  Instead place all dirty buffers into the
> I/O queue and add a write barrier.  This ensures that
> no subsequent write will reach the disk before all the
> recovery writes, but that we do not have to wait for the
> I/O.
> 
> +	/*
> +	 * Set an option to indicate that we want to mount fast even
> +	 * when recovering.  That is achieved by not sync'ing the
> +	 * block device, but instead placing all dirty buffers into
> +	 * the I/O queue and adding a write barrier.
> +	 */
> +	set_opt(sbi->s_mount_opt, FAST);

Is there ever a time where one wouldn't want to do a fast mount?
Surely if this speeds things up and is safe, it makes sense to do
it always.  If it isn't safe to do always, then would you EVER want
to do it if you risk corrupting your filesystem?

Cheers, Andreas
--
Andreas Dilger
Sr. Staff Engineer, Lustre Group
Sun Microsystems of Canada, Inc.


  reply	other threads:[~2009-07-14 21:22 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-07-14 14:02 [PATCH 0/2] ext3 HACKs Adrian Hunter
2009-07-14 14:03 ` [PATCH 1/2] HACK: ext3: mount fast even when recovering Adrian Hunter
2009-07-14 21:22   ` Andreas Dilger [this message]
2009-07-15 15:35     ` Adrian Hunter
2009-07-14 14:03 ` [PATCH 2/2] HACK: do I/O read requests while ext3 journal recovers Adrian Hunter
2009-07-14 21:26   ` Andreas Dilger
2009-07-15 15:35     ` Adrian Hunter
2009-07-14 15:51 ` [PATCH 0/2] ext3 HACKs Theodore Tso
  -- strict thread matches above, loose matches on Subject: below --
2009-07-14 14:05 Adrian Hunter
2009-07-14 14:05 ` [PATCH 1/2] HACK: ext3: mount fast even when recovering Adrian Hunter
2009-07-14 21:34   ` Andrew Morton
2009-07-14 21:46     ` Eric Sandeen
2009-07-14 22:36       ` Theodore Tso
2009-07-15 15:35         ` Adrian Hunter
2009-07-15  5:53     ` Artem Bityutskiy
2009-07-15 15:35     ` Adrian Hunter

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=20090714212221.GD4829@webber.adilger.int \
    --to=adilger@sun.com \
    --cc=adrian.hunter@nokia.com \
    --cc=akpm@linux-foundation.org \
    --cc=artem.bityutskiy@nokia.com \
    --cc=linux-ext4@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).