On Mon, Apr 07, 2008 at 10:33:19PM +0200, Thor Kristoffersen wrote:
> Timothy Shimmin <tes@xxxxxxx> writes:
> > Thor Kristoffersen wrote:
> >>> 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?
> 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).
SGI Australian Software Group