public inbox for linux-xfs@vger.kernel.org
 help / color / mirror / Atom feed
From: David Chinner <dgc@sgi.com>
To: Timothy Shimmin <tes@sgi.com>
Cc: David Chinner <dgc@sgi.com>, Barry Naujok <bnaujok@sgi.com>,
	xfs-dev <xfs-dev@sgi.com>, xfs-oss <xfs@oss.sgi.com>
Subject: Re: [patch] remove unnecessary periodic superblock logging.
Date: Thu, 10 Apr 2008 15:49:13 +1000	[thread overview]
Message-ID: <20080410054913.GL108924158@sgi.com> (raw)
In-Reply-To: <47FDA5BA.3080401@sgi.com>

On Thu, Apr 10, 2008 at 03:29:30PM +1000, Timothy Shimmin wrote:
> Barry Naujok wrote:
> >On Thu, 10 Apr 2008 14:20:01 +1000, David Chinner <dgc@sgi.com> wrote:
> >
> >>Remove periodic logging of in-core superblock counters.
> >>
> >>xfssyncd triggers the logging of superblock counters every
> >>30s if the filesystem is made with lazy-count=1. This will
> >>prevent disks from idling and spinning down as there will
> >>be a log write every 30s. With the way counter recovery
> >>works for lazy-count=1, this code is unnecessary and provides
> >>no real benefit, so just remove it.
> >
> >I'm happy with this (xfs_initialize_perag_data() does the
> >global counter recovery during mount).
> >
> 
> So we only do the sb count logging at unmount type times...
> xfs_attr_quiesce() and xfs_unmountfs(),
> when no log recovery will happen.
> Hmmm...so why do we have to log it out at these times?
> I'm forgetting how this works.

xfs_log_sbcount() sync's the incore counters to the superblock
buffer transactionally. Not strictly necessary, but for consistency
with other superblock updates.....

Cheers,

Dave.
-- 
Dave Chinner
Principal Engineer
SGI Australian Software Group

      reply	other threads:[~2008-04-10  5:48 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-04-10  4:20 [patch] remove unnecessary periodic superblock logging David Chinner
2008-04-10  4:49 ` Barry Naujok
2008-04-10  5:29   ` Timothy Shimmin
2008-04-10  5:49     ` David Chinner [this message]

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=20080410054913.GL108924158@sgi.com \
    --to=dgc@sgi.com \
    --cc=bnaujok@sgi.com \
    --cc=tes@sgi.com \
    --cc=xfs-dev@sgi.com \
    --cc=xfs@oss.sgi.com \
    /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