From: Thor Kristoffersen <thorkr@gmail.com>
To: David Chinner <dgc@sgi.com>
Cc: Timothy Shimmin <tes@sgi.com>, xfs@oss.sgi.com
Subject: Re: Does XFS prevent disk spindown?
Date: Tue, 08 Apr 2008 07:53:13 +0200 [thread overview]
Message-ID: <m2skxwriye.fsf@getmail.no> (raw)
In-Reply-To: <20080407215855.GE108924158@sgi.com>
David Chinner <dgc@sgi.com> writes:
>> > What does 'xfs_logprint -t' show in these "idle" states
>> > after these writes?
>>
>> xfs_logprint produces output like the one shown below, so it does indeed
>> look like it's writing to the journal. But why should it need to keep
>> writing to the journal when there have been no updates to any files on that
>> partition recently?
>
> Are you using lazy-count=1? (i.e. output of 'xfs_info <mtpt>', please).
Looks like I am:
meta-data=/dev/sda3 isize=256 agcount=4, agsize=42676171 blks
= sectsz=512 attr=2
data = bsize=4096 blocks=170704681, imaxpct=25
= sunit=0 swidth=0 blks
naming =version 2 bsize=4096
log =internal bsize=4096 blocks=32768, version=2
= 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.
Thor
next prev parent reply other threads:[~2008-04-08 5:53 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 [this message]
2008-04-09 4:11 ` [patch] " David Chinner
2008-04-09 21:32 ` Thor Kristoffersen
2008-04-09 23:02 ` David Chinner
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=m2skxwriye.fsf@getmail.no \
--to=thorkr@gmail.com \
--cc=dgc@sgi.com \
--cc=tes@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