| To: | David Chinner <dgc@xxxxxxx> |
|---|---|
| Subject: | Re: Does XFS prevent disk spindown? |
| From: | Thor Kristoffersen <thorkr@xxxxxxxxx> |
| Date: | Tue, 08 Apr 2008 07:53:13 +0200 |
| Cc: | Timothy Shimmin <tes@xxxxxxx>, xfs@xxxxxxxxxxx |
| In-reply-to: | <20080407215855.GE108924158@sgi.com> |
| References: | <m2tzimbvif.fsf@getmail.no> <20080401003005.GJ103491721@sgi.com> <47F1CF6D.2040103@sandeen.net> <m2d4p9o2sc.fsf@getmail.no> <m2y77smmdj.fsf@getmail.no> <47F9735E.8020900@sgi.com> <m2wsn9qub4.fsf@getmail.no> <20080407215855.GE108924158@sgi.com> |
| Sender: | xfs-bounce@xxxxxxxxxxx |
| User-agent: | Gnus/5.11 (Gnus v5.11) Emacs/22.1 (gnu/linux) |
David Chinner <dgc@xxxxxxx> 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
|
| <Prev in Thread] | Current Thread | [Next in Thread> |
|---|---|---|
| ||
| Previous by Date: | Lost+found, Jeffrey Sandel |
|---|---|
| Next by Date: | Re: [REVIEW] cleanup - remove bhv_vname_t, Christoph Hellwig |
| Previous by Thread: | Re: Does XFS prevent disk spindown?, David Chinner |
| Next by Thread: | [patch] Re: Does XFS prevent disk spindown?, David Chinner |
| Indexes: | [Date] [Thread] [Top] [All Lists] |