From: Timothy Shimmin <tes@sgi.com>
To: Thor Kristoffersen <thorkr@gmail.com>
Cc: xfs@oss.sgi.com
Subject: Re: Does XFS prevent disk spindown?
Date: Mon, 07 Apr 2008 11:05:34 +1000 [thread overview]
Message-ID: <47F9735E.8020900@sgi.com> (raw)
In-Reply-To: <m2y77smmdj.fsf@getmail.no>
Thor Kristoffersen wrote:
> (It looks like my reply never made it to the list so I'm trying again.)
>
> Eric Sandeen <sandeen@sandeen.net> writes:
>> David Chinner wrote:
>>> On Mon, Mar 31, 2008 at 08:26:00PM +0200, Thor Kristoffersen wrote:
>>>> I've noticed that when I spin down XFS-mounted disks they spin up again
>>>> shortly afterwards. I used iostat to monitor disk accesses to a mounted
>>>> partition (with noatime) in single user mode. Apparently there is a write
>>>> access to the partition approximately every 35 seconds, even if the
>>>> partition is idle. As far as I can understand, since there is no data that
>>>> needs to be flushed this must be done by an XFS daemon for some purpose.
>> Use blktrace, or echo 1 > /proc/sys/vm/block_dump to see what block and
>> who's writing it... it's probably the superblock? what kernel?
>
> This is kernel version 2.6.24. More specifically it's a Debian kernel from
> package linux-image-2.6.24-1-686 (2.6.24-4).
>
> I put the system in runlevel 1 and executed the test as you suggested. On
> /dev/sda3 I have mounted (with noatime) an XFS filesystem that contains
> data that is not supposed to be accessed by any process. In the output
> below I have filtered out all accesses to other partitions. (BTW, this is
> not actually the disk that I wanted to spin down, but I think the log
> proves my point.)
>
>
I'm wondering if that is writing to the xfs ondisk log/journal in those cases.
What does 'xfs_logprint -t' show in these "idle" states
after these writes?
--Tim
> Thor
>
> ------------------------------------------------------
>
> Tue Apr 1 18:51:27 CEST 2008
> xfssyncd(3426): WRITE block 682946473 on sda3
> Tue Apr 1 18:51:32 CEST 2008
> Tue Apr 1 18:51:37 CEST 2008
> Tue Apr 1 18:51:42 CEST 2008
> Tue Apr 1 18:51:47 CEST 2008
> Tue Apr 1 18:51:52 CEST 2008
> Tue Apr 1 18:51:57 CEST 2008
> Tue Apr 1 18:52:02 CEST 2008
> xfssyncd(3426): WRITE block 682946475 on sda3
> Tue Apr 1 18:52:07 CEST 2008
> Tue Apr 1 18:52:12 CEST 2008
> Tue Apr 1 18:52:17 CEST 2008
> Tue Apr 1 18:52:22 CEST 2008
> Tue Apr 1 18:52:27 CEST 2008
> Tue Apr 1 18:52:32 CEST 2008
> Tue Apr 1 18:52:37 CEST 2008
> Tue Apr 1 18:52:42 CEST 2008
> xfssyncd(3426): WRITE block 682946477 on sda3
> Tue Apr 1 18:52:47 CEST 2008
> Tue Apr 1 18:52:52 CEST 2008
> Tue Apr 1 18:52:57 CEST 2008
> Tue Apr 1 18:53:02 CEST 2008
> Tue Apr 1 18:53:07 CEST 2008
> Tue Apr 1 18:53:12 CEST 2008
> Tue Apr 1 18:53:17 CEST 2008
> xfssyncd(3426): WRITE block 682946479 on sda3
> Tue Apr 1 18:53:22 CEST 2008
> Tue Apr 1 18:53:27 CEST 2008
> Tue Apr 1 18:53:32 CEST 2008
> Tue Apr 1 18:53:37 CEST 2008
> Tue Apr 1 18:53:42 CEST 2008
> Tue Apr 1 18:53:47 CEST 2008
> Tue Apr 1 18:53:52 CEST 2008
> xfssyncd(3426): WRITE block 682946481 on sda3
> Tue Apr 1 18:53:57 CEST 2008
> Tue Apr 1 18:54:02 CEST 2008
> Tue Apr 1 18:54:07 CEST 2008
> Tue Apr 1 18:54:12 CEST 2008
> Tue Apr 1 18:54:17 CEST 2008
> Tue Apr 1 18:54:22 CEST 2008
> Tue Apr 1 18:54:27 CEST 2008
> xfssyncd(3426): WRITE block 682946483 on sda3
> Tue Apr 1 18:54:32 CEST 2008
> Tue Apr 1 18:54:37 CEST 2008
> Tue Apr 1 18:54:42 CEST 2008
> Tue Apr 1 18:54:47 CEST 2008
> Tue Apr 1 18:54:52 CEST 2008
> Tue Apr 1 18:54:57 CEST 2008
> Tue Apr 1 18:55:02 CEST 2008
> xfssyncd(3426): WRITE block 682946485 on sda3
> Tue Apr 1 18:55:07 CEST 2008
> Tue Apr 1 18:55:12 CEST 2008
> Tue Apr 1 18:55:17 CEST 2008
> Tue Apr 1 18:55:22 CEST 2008
> Tue Apr 1 18:55:27 CEST 2008
> Tue Apr 1 18:55:32 CEST 2008
> Tue Apr 1 18:55:37 CEST 2008
> xfssyncd(3426): WRITE block 682946487 on sda3
> Tue Apr 1 18:55:42 CEST 2008
> Tue Apr 1 18:55:47 CEST 2008
> Tue Apr 1 18:55:52 CEST 2008
> Tue Apr 1 18:55:57 CEST 2008
> Tue Apr 1 18:56:02 CEST 2008
> Tue Apr 1 18:56:07 CEST 2008
> Tue Apr 1 18:56:12 CEST 2008
> Tue Apr 1 18:56:17 CEST 2008
> xfssyncd(3426): WRITE block 682946489 on sda3
> Tue Apr 1 18:56:22 CEST 2008
> Tue Apr 1 18:56:27 CEST 2008
> Tue Apr 1 18:56:32 CEST 2008
> Tue Apr 1 18:56:37 CEST 2008
> Tue Apr 1 18:56:42 CEST 2008
> Tue Apr 1 18:56:47 CEST 2008
> Tue Apr 1 18:56:52 CEST 2008
> xfssyncd(3426): WRITE block 682946491 on sda3
> Tue Apr 1 18:56:57 CEST 2008
> Tue Apr 1 18:57:02 CEST 2008
> Tue Apr 1 18:57:07 CEST 2008
> Tue Apr 1 18:57:12 CEST 2008
> Tue Apr 1 18:57:17 CEST 2008
> Tue Apr 1 18:57:22 CEST 2008
> Tue Apr 1 18:57:27 CEST 2008
> xfssyncd(3426): WRITE block 682946493 on sda3
> Tue Apr 1 18:57:32 CEST 2008
> Tue Apr 1 18:57:37 CEST 2008
> Tue Apr 1 18:57:42 CEST 2008
> Tue Apr 1 18:57:47 CEST 2008
> Tue Apr 1 18:57:52 CEST 2008
> Tue Apr 1 18:57:57 CEST 2008
> Tue Apr 1 18:58:02 CEST 2008
> xfssyncd(3426): WRITE block 682946495 on sda3
> Tue Apr 1 18:58:07 CEST 2008
> Tue Apr 1 18:58:12 CEST 2008
> Tue Apr 1 18:58:17 CEST 2008
> Tue Apr 1 18:58:22 CEST 2008
>
next prev parent reply other threads:[~2008-04-07 1:05 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 [this message]
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
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=47F9735E.8020900@sgi.com \
--to=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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.