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: <20081215214911.3E1DA108042@picon.linux-foundation.org>
Date:	Mon, 15 Dec 2008 13:49:11 -0800 (PST)
From:	bugme-daemon@...zilla.kernel.org
To:	linux-ext4@...r.kernel.org
Subject: [Bug 12224] journal activity on inactive partition causes inactive harddrive spinup

http://bugzilla.kernel.org/show_bug.cgi?id=12224





------- Comment #7 from csights@...tmail.fm  2008-12-15 13:49 -------
Hi,
        Following Ted's suggestion, I began with 2.6.27.6 and then reversed the
patch 
for commit a0b8bfb34743b6e6c2bb06ad5a270590d90270f7.  This "fixed" the 
problem such that activity on hda1 no longer caused kjournald to write to 
sda1.




> Is /dev/sda1 even mounted?  It doesn't included up in your /etc/mtab
> listing.

Just to confirm, I posted the wrong mtab previously.  sda1 is mounted during 
my tests.  This is how it looks:

/dev/hda1 on / type ext3 (rw,noatime,errors=remount-ro,commit=1209600)
tmpfs on /lib/init/rw type tmpfs (rw,nosuid,mode=0755)
proc on /proc type proc (rw,noexec,nosuid,nodev)
sysfs on /sys type sysfs (rw,noexec,nosuid,nodev)
udev on /dev type tmpfs (rw,mode=0755)
tmpfs on /dev/shm type tmpfs (rw,nosuid,nodev)
devpts on /dev/pts type devpts (rw,noexec,nosuid,gid=5,mode=620)
/dev/sda1 on /mnt/sda type ext3 (rw,noatime,commit=1209600)
debugfs on /sys/kernel/debug type debugfs (rw)



> ------- Comment #6 from sandeen@...hat.com  2008-12-14 21:07 -------
>
> Dec 14 20:02:18 localhost kernel: kjournald(1109): WRITE block 12520 on
> sda1
>
> is the first thing I see in the log above, with no indication of anything
> else on sda1 before that.

        I only copied the lines from the log during the short compile "test".
        Here is another test which is a little more clean, using 2.6.27.6
(without 
the commit mentioned above reverted). 

        First unmount, then remount /dev/sda1 to flush the filesystem caches:
# umount /dev/sda1; mount /mnt/sda; btrace /dev/sda | logger -s

        then switch to another console and restart laptop mode (to change the
commit 
time on sda1):
#/etc/init.d/laptop-mode restart

        Finally generate some activity on hda1.  ("make menuconfig")
        The following is syslog from the mount of /dev/sda1 (on /mnt/sda) until
"make 
clean" finished:

Dec 15 16:34:48 localhost kernel: kjournald starting.  Commit interval 5 
seconds
Dec 15 16:34:48 localhost kernel: EXT3 FS on sda1, internal journal
Dec 15 16:34:48 localhost kernel: EXT3-fs: mounted filesystem with ordered 
data mode.
Dec 15 16:34:54 localhost kernel: hda: cache flushes not supported
Dec 15 16:34:56 localhost kernel: hda: cache flushes not supported
Dec 15 16:34:57 localhost logger:   8,0    0        1     0.000000000  4140  A  
WS 12423 + 8 <- (8,1) 12360
Dec 15 16:34:57 localhost logger:   8,0    0        2     0.000006146  4140  Q  
WS 12423 + 8 [kjournald]
Dec 15 16:34:57 localhost logger:   8,0    0        3     0.000114819  4140  G  
WS 12423 + 8 [kjournald]
Dec 15 16:34:57 localhost logger:   8,0    0        4     0.000143314  4140  P  
N [kjournald]
Dec 15 16:34:57 localhost logger:   8,0    0        5     0.000159797  4140  I  
W 12423 + 8 [kjournald]
Dec 15 16:34:57 localhost logger:   8,0    0        6     0.000348089  4140  D  
W 12423 + 8 [kjournald]
Dec 15 16:34:57 localhost logger:   8,0    0        7     0.000463746  4140  U  
N [kjournald] 1
Dec 15 16:34:57 localhost logger:   8,0    0        8     0.010034518     3  C  
W 12423 + 8 [0]
Dec 15 16:34:57 localhost logger:   8,0    0        9     0.010557490  4140  A  
WS 12431 + 8 <- (8,1) 12368
Dec 15 16:34:57 localhost logger:   8,0    0       10     0.010563916  4140  Q  
WS 12431 + 8 [kjournald]
Dec 15 16:34:57 localhost logger:   8,0    0       11     0.010589617  4140  G  
WS 12431 + 8 [kjournald]
Dec 15 16:34:57 localhost logger:   8,0    0       12     0.010606658  4140  P  
N [kjournald]
Dec 15 16:34:57 localhost logger:   8,0    0       13     0.010616157  4140  I  
W 12431 + 8 [kjournald]
Dec 15 16:34:57 localhost logger:   8,0    0       14     0.010749414  4140  D  
W 12431 + 8 [kjournald]
Dec 15 16:34:57 localhost logger:   8,0    0       15     0.010836297  4140  U  
N [kjournald] 1
Dec 15 16:34:57 localhost logger:   8,0    0       16     0.021000161     3  C  
W 12431 + 8 [0]
Dec 15 16:34:59 localhost logger:   8,0    0       17     2.350235673  4140  A  
WS 12439 + 8 <- (8,1) 12376
Dec 15 16:34:59 localhost logger:   8,0    0       18     2.350244612  4140  Q  
WS 12439 + 8 [kjournald]
Dec 15 16:34:59 localhost logger:   8,0    0       19     2.350278974  4140  G  
WS 12439 + 8 [kjournald]
Dec 15 16:34:59 localhost logger:   8,0    0       20     2.350301044  4140  P  
N [kjournald]
Dec 15 16:34:59 localhost logger:   8,0    0       21     2.350316130  4140  I  
W 12439 + 8 [kjournald]
Dec 15 16:34:59 localhost logger:   8,0    0       22     2.350568397  4140  D  
W 12439 + 8 [kjournald]
Dec 15 16:34:59 localhost logger:   8,0    0       23     2.350684333  4140  U  
N [kjournald] 1
Dec 15 16:34:59 localhost logger:   8,0    0       24     2.360609899     3  C  
W 12439 + 8 [0]
Dec 15 16:35:52 localhost logger:   8,0    0       25    55.121164875  4140  A  
WS 12447 + 8 <- (8,1) 12384
Dec 15 16:35:52 localhost logger:   8,0    0       26    55.121172697  4140  Q  
WS 12447 + 8 [kjournald]
Dec 15 16:35:52 localhost logger:   8,0    0       27    55.121203707  4140  G  
WS 12447 + 8 [kjournald]
Dec 15 16:35:52 localhost logger:   8,0    0       28    55.121221865  4140  P  
N [kjournald]
Dec 15 16:35:52 localhost logger:   8,0    0       29    55.121232202  4140  I  
W 12447 + 8 [kjournald]
Dec 15 16:35:52 localhost logger:   8,0    0       30    55.121458767  4140  D  
W 12447 + 8 [kjournald]
Dec 15 16:35:52 localhost logger:   8,0    0       31    55.121571910  4140  U  
N [kjournald] 1
Dec 15 16:35:52 localhost logger:   8,0    0       32    55.131824892     3  C  
W 12447 + 8 [0]
Dec 15 16:35:57 localhost logger:   8,0    0       33    59.696845185  4140  A  
WS 12455 + 8 <- (8,1) 12392
Dec 15 16:35:57 localhost logger:   8,0    0       34    59.696853566  4140  Q  
WS 12455 + 8 [kjournald]
Dec 15 16:35:57 localhost logger:   8,0    0       35    59.696888486  4140  G  
WS 12455 + 8 [kjournald]
Dec 15 16:35:57 localhost logger:   8,0    0       36    59.696908880  4140  P  
N [kjournald]
Dec 15 16:35:57 localhost logger:   8,0    0       37    59.696920334  4140  I  
W 12455 + 8 [kjournald]
Dec 15 16:35:57 localhost logger:   8,0    0       38    59.697142709  4140  D  
W 12455 + 8 [kjournald]
Dec 15 16:35:57 localhost logger:   8,0    0       39    59.697256410  4140  U  
N [kjournald] 1
Dec 15 16:35:57 localhost logger:   8,0    0       40    59.707057938     3  C  
W 12455 + 8 [0]
Dec 15 16:36:04 localhost logger:   8,0    0       41    67.363585697  4140  A  
WS 12463 + 8 <- (8,1) 12400
Dec 15 16:36:04 localhost logger:   8,0    0       42    67.363595196  4140  Q  
WS 12463 + 8 [kjournald]
Dec 15 16:36:04 localhost logger:   8,0    0       43    67.363627043  4140  G  
WS 12463 + 8 [kjournald]
Dec 15 16:36:04 localhost logger:   8,0    0       44    67.363646319  4140  P  
N [kjournald]
Dec 15 16:36:04 localhost logger:   8,0    0       45    67.363657215  4140  I  
W 12463 + 8 [kjournald]
Dec 15 16:36:04 localhost logger:   8,0    0       46    67.363869253  4140  D  
W 12463 + 8 [kjournald]
Dec 15 16:36:04 localhost logger:   8,0    0       47    67.363980161  4140  U  
N [kjournald] 1
Dec 15 16:36:04 localhost logger:   8,0    0       48    67.373786717     3  C  
W 12463 + 8 [0]

>
> If you let the system just sit idle, do you get sda1 hits from the sysctl
> and/or blktrace?

        If I let the system sit idle using 2.6.27.5 (the last unaffected 
version) 'btrace /dev/sda' shows no activity, even if there is activity on 
hda1.
        If I let the system sit idle using 2.6.27.6 (the first affected 
version) 'btrace /dev/sda' shows kjournald doing something with sda1 if there 
is activity on hda1.  If hda1 is inactive then there is also no activity on 
sda1.

Thanks!
        C.


-- 
Configure bugmail: http://bugzilla.kernel.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.
--
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

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ