linux-ext4 - Re: [Bug 12224] journal activity on inactive partition causes inactive harddrive spinup

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <4945925C.8010606@redhat.com>
Date:	Sun, 14 Dec 2008 17:10:20 -0600
From:	Eric Sandeen <sandeen@...hat.com>
To:	bugme-daemon@...zilla.kernel.org
CC:	linux-ext4@...r.kernel.org
Subject: Re: [Bug 12224] journal activity on inactive partition causes inactive
 harddrive spinup

bugme-daemon@...zilla.kernel.org wrote:

> OK, that's a huge mess because bugzilla went and wordwrapped it.  Let
> me fix it:
> 
>> Dec   9 11:15:32 localhost logger:    8,0      0            1       0.000000000    1109   A   WS 14375 + 8 <- (8,1) 14312
>> Dec   9 11:15:32 localhost logger:    8,0      0            2       0.000006705   1109   Q   WS 14375 + 8 [kjournald]
>> Dec   9 11:15:32 localhost logger:    8,0      0            3       0.000043581   1109   G   WS 14375 + 8 [kjournald] 
>> Dec   9 11:15:32 localhost logger:    8,0      0            4       0.000065651   1109   P    N [kjournald]
>> Dec   9 11:15:32 localhost logger:    8,0      0            5       0.000076267   1109   I    W 14375 + 8 [kjournald]
>> Dec   9 11:15:32 localhost logger:    8,0      0            6       0.000300318   1109   D    W 14375 + 8 [kjournald]
>> Dec   9 11:15:32 localhost logger:    8,0      0            7       0.000423518   1109   U    N [kjournald] 1
>> Dec   9 11:15:32 localhost logger:    8,0      0            8       0.010028373      3   C    W 14375 + 8 [0]
>> Dec   9 11:15:35 localhost logger:    8,0      0            9       3.219049689   1109   A   WS 14383 + 8 <- (8,1) 14320
>> Dec   9 11:15:35 localhost logger:    8,0      0           10       3.219058350   1109   Q   WS 14383 + 8 [kjournald]
>> Dec   9 11:15:35 localhost logger:    8,0      0           11       3.219095505   1109   G   WS 14383 + 8 [kjournald]
>> Dec   9 11:15:35 localhost logger:    8,0      0           12       3.219115061   1109   P    N [kjournald]
>> Dec   9 11:15:35 localhost logger:    8,0      0           13       3.219127074   1109   I    W 14383 + 8 [kjournald]
>> Dec   9 11:15:35 localhost logger:    8,0      0           14       3.219344699   1109   D    W 14383 + 8 [kjournald]
>> Dec   9 11:15:35 localhost logger:    8,0      0           15       3.219543607   1109   U    N [kjournald] 1
>> Dec   9 11:15:35 localhost logger:    8,0      0           16       3.229477275       3   C    W 14383 + 8 [0]
> 
> I'm not familar with btrace.  What are we looking at here?

Andrew, it's blktrace/blkparse output, basically.  blkparse(1) manpage
has the details.

maj,min cpu  seq  time           pid   act rwbs off+len
8,0      0    1   0.000000000    1109   A   WS 14375 + 8 <- (8,1) 14312

... etc

I'm not sure it gives us enough info; all we see is that there was an IO
on sdb (from sdb1)

I might suggest

# sysctl -w vm.block_dump=1

to see if you get any info about inodes on sda1 being dirtied.

(Also, I didn't see any info about sda1 in the posted fstab...)

-Eric


--
To unsubscribe from this list: send the line "unsubscribe linux-ext4" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html