public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: "Stephen C. Tweedie" <sct@redhat.com>
To: Andrew Morton <akpm@zip.com.au>,
	LKML <linux-kernel@vger.kernel.org>,
	Stephen Tweedie <sct@redhat.com>
Subject: Re: Automatically mount or remount EXT3 partitions with EXT2 when alaptop is powered by a battery?
Date: Tue, 2 Jul 2002 13:13:14 +0100	[thread overview]
Message-ID: <20020702131314.B4711@redhat.com> (raw)
In-Reply-To: <20020628215942.GA3679@pelks01.extern.uni-tuebingen.de>; from kobras@tat.physik.uni-tuebingen.de on Fri, Jun 28, 2002 at 11:59:42PM +0200

Hi,

On Fri, Jun 28, 2002 at 11:59:42PM +0200, Daniel Kobras wrote:
> On Tue, Jun 25, 2002 at 10:03:47AM -0700, Andrew Morton wrote:
> > If it's because of the disk-spins-up-too-much problem then
> > that can be addressed by allowing the commit interval to be
> > set to larger values.
> 
> The updated commit interval will only affect new transactions, correct?
> In other words, when changing the commit interval from t_old to t_new,
> it will take t_old seconds until we can be certain there are only
> transactions with a t_new expiry interval in the queue?

Yes, unless:
> Or is there a
> way to flush the current queue of transactions, eg. by fsync()ing the
> underlying block device, or by sending a magic signal to kjournald? 

an fsync() on any file or directory on the filesystem will ensure that
all old transactions have completed, and a sync() will ensure that any
old transactions are at least on their way to disk.

Cheers,
 Stephen

  reply	other threads:[~2002-07-02 12:10 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-06-24 20:02 Automatically mount or remount EXT3 partitions with EXT2 when a laptop is powered by a battery? Miles Lane
2002-06-24 20:23 ` Andreas Dilger
2002-06-24 20:27 ` Richard B. Johnson
2002-06-25 17:03 ` Automatically mount or remount EXT3 partitions with EXT2 when alaptop " Andrew Morton
2002-06-25 17:24   ` Miles Lane
2002-06-25 19:35     ` Andrew Morton
2002-07-03  3:02       ` Pavel Machek
2002-06-26  0:13   ` Stephen Tweedie
2002-06-26 18:39     ` Andrew Morton
2002-07-02 13:23       ` Stephen C. Tweedie
2002-07-03  3:04         ` Pavel Machek
2002-06-28 21:59   ` Daniel Kobras
2002-07-02 12:13     ` Stephen C. Tweedie [this message]
2002-07-03  3:04       ` Pavel Machek
2002-07-04 20:30         ` Stephen Tweedie
2002-07-04 22:05       ` Daniel Kobras
2002-07-05  7:59         ` Stephen Tweedie
2002-07-06  0:58           ` Pavel Machek
2002-07-23 11:14             ` Stephen C. Tweedie

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=20020702131314.B4711@redhat.com \
    --to=sct@redhat.com \
    --cc=akpm@zip.com.au \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox