From: David Chinner <dgc@sgi.com>
To: Thor Kristoffersen <thorkr@gmail.com>
Cc: David Chinner <dgc@sgi.com>, Timothy Shimmin <tes@sgi.com>,
xfs@oss.sgi.com
Subject: Re: [patch] Re: Does XFS prevent disk spindown?
Date: Thu, 10 Apr 2008 09:02:19 +1000 [thread overview]
Message-ID: <20080409230219.GM108924158@sgi.com> (raw)
In-Reply-To: <m21w5eiuj1.fsf@getmail.no>
On Wed, Apr 09, 2008 at 11:32:34PM +0200, Thor Kristoffersen wrote:
> David Chinner <dgc@sgi.com> writes:
> >> = sectsz=512 sunit=0 blks, lazy-count=1
> >> realtime =none extsz=4096 blocks=0, rtextents=0
> >>
> >> Is that what's causing it? I have never specified any lazy-count option
> >> when I created or mounted the filesystem. I didn't even know it existed.
> >
> > Introduced in 2.6.22, and recently was made the default mkfs config.
> >
> > Try the patch below.
>
> Thanks a lot, David! Your patch worked perfectly. Also thanks to the
> others who helped me track down this issue.
Cool. I'll get that patch reviewed and checked in, then.
> BTW, what are the consequences of setting lazy-count to 0? Less safety?
> Reduced performance?
One a single disk? No difference to performance, but significantly
lower latency on metadata operations is seen when using lazy-count=1.
If you have lots of disks, or low-latency caches in front of your disks,
lazy-count=1 will prevent superblock updates from being the metadata
performance limiting factor.
Cheers,
Dave.
--
Dave Chinner
Principal Engineer
SGI Australian Software Group
prev parent reply other threads:[~2008-04-09 23:01 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-03-31 18:26 Does XFS prevent disk spindown? Thor Kristoffersen
2008-04-01 0:30 ` David Chinner
2008-04-01 6:00 ` Eric Sandeen
2008-04-01 18:20 ` Thor Kristoffersen
2008-04-05 14:01 ` Thor Kristoffersen
2008-04-07 1:05 ` Timothy Shimmin
2008-04-07 20:33 ` Thor Kristoffersen
2008-04-07 21:58 ` David Chinner
2008-04-08 5:53 ` Thor Kristoffersen
2008-04-09 4:11 ` [patch] " David Chinner
2008-04-09 21:32 ` Thor Kristoffersen
2008-04-09 23:02 ` 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=20080409230219.GM108924158@sgi.com \
--to=dgc@sgi.com \
--cc=tes@sgi.com \
--cc=thorkr@gmail.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