public inbox for linux-xfs@vger.kernel.org
 help / color / mirror / Atom feed
From: Andy Bennett <andyjpb@ashurst.eu.org>
To: Dave Chinner <david@fromorbit.com>
Cc: xfs@oss.sgi.com
Subject: Re: Disk spin down
Date: Sun, 12 Feb 2012 21:28:32 +0000	[thread overview]
Message-ID: <4F382F00.9040100@ashurst.eu.org> (raw)
In-Reply-To: <4F382BDF.3070901@ashurst.eu.org>

[-- Attachment #1: Type: text/plain, Size: 1355 bytes --]

Hi,

>> Seems to me that something is still dirtying an inode regularly.
>>
>> Perhaps you need to look at the XFS and writeback event traces to
>> find out what process is dirtying the inode. trace-cmd is your
>> friend...
> 
> Something like this?
> 
> -----
> echo 1 > /sys/kernel/debug/tracing/events/xfs/enable
> 
> echo 0 > /sys/kernel/debug/tracing/events/xfs/enable
> 
> more /sys/kernel/debug/tracing/trace
> -----
> 
> 
> I tried recreating the situation of the last 2 days (clean boot, stopped
> services) and it's currently quiescing nicely. :-(
> 
> I'll keep an eye on it and try to catch it in the act but every time I
> turn the tracing on the HDD light stays firmly off. :-(

There is more interesting news already.

I had used 'hdparm -S 120' to set the spindown_timeout to 10 minutes. It
appears that that was sticking through a cold boot. Setting that back to
its previous value of 1 (5 seconds) makes the disk constantly spin up
and down when I suspect it is idle.

I've caught a trace over the course of a few spinup/downs and attached
it (gzipped as it's 208K unpacked).

When the spindown_timeout was set to 10 minutes I managed to run the
trace for a minute without logging anything. When the spindown_timeout
is 5 seconds much more is logged.





Regards,
@ndy

-- 
andyjpb@ashurst.eu.org
http://www.ashurst.eu.org/
0x7EBA75FF


[-- Attachment #2: trace.gz --]
[-- Type: application/gzip, Size: 14229 bytes --]

[-- Attachment #3: Type: text/plain, Size: 121 bytes --]

_______________________________________________
xfs mailing list
xfs@oss.sgi.com
http://oss.sgi.com/mailman/listinfo/xfs

  reply	other threads:[~2012-02-12 21:28 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-02-12 18:23 Disk spin down Andy Bennett
2012-02-12 20:06 ` Dave Chinner
2012-02-12 21:15   ` Andy Bennett
2012-02-12 21:28     ` Andy Bennett [this message]
2012-02-12 22:35       ` Dave Chinner
2012-02-12 22:57         ` Andy Bennett
2012-02-13  8:36 ` Brian Candler
2012-02-13 23:41   ` Dave 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=4F382F00.9040100@ashurst.eu.org \
    --to=andyjpb@ashurst.eu.org \
    --cc=david@fromorbit.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