linux-ext4.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: bugme-daemon@bugzilla.kernel.org
To: linux-ext4@vger.kernel.org
Subject: [Bug 12224] journal activity on inactive partition causes inactive harddrive spinup
Date: Tue, 16 Dec 2008 18:30:08 -0800 (PST)	[thread overview]
Message-ID: <20081217023008.54CF111D108@picon.linux-foundation.org> (raw)
In-Reply-To: <bug-12224-13602@http.bugzilla.kernel.org/>

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





------- Comment #10 from csights@fastmail.fm  2008-12-16 18:30 -------
On Tuesday 16 December 2008 17:01:27 bugme-daemon@bugzilla.kernel.org wrote:
> http://bugzilla.kernel.org/show_bug.cgi?id=12224


> ------- Comment #9 from sandeen@redhat.com  2008-12-16 14:01 -------
> Are the laptop-mode tools doing remounts behind your back?
>
> The only way I see this is if I do "mount -o remount /"; then I see
> kjournald activity on other ext3 filesystems.  I'll dig into that.

I don't think so: I was able to reproduce this bug using an ext3 loopback 
mounted file.  laptop-mode-tools does not touch loopback devices as far as I 
can tell.  Here is my laptop-mode.conf:

> #
> # The drives that laptop mode controls.
> # Separate them by a space, e.g. HD="/dev/hda /dev/hdb". The default is a
> # wildcard, which will get you all your IDE and SCSI/SATA drives.
> #
> HD="/dev/[hs]d[abcdefgh]"

        And here is the loopback mount:

/tmp/ext3Image on /mnt/loop type ext3 
(rw,noatime,loop=/dev/loop/0,commit=1209600)

        (I set the commit=1209600 and noatime by hand on the loopback mounted
ext3 
image file.)

        Since I'm not a kernel hacker, I don't know how the code is structured.
 It 
feels like the kernel commit code is not fully separated by device (or 
partition). When the active partition's journal is "synced" it triggers 
activity on other partitions, even if the other partitions aren't active.

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.

  parent reply	other threads:[~2008-12-17  2:30 UTC|newest]

Thread overview: 28+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-12-14 19:39 [Bug 12224] New: journal activity on inactive partition causes inactive harddrive spinup bugme-daemon
2008-12-14 22:29 ` [Bug 12224] " bugme-daemon
2008-12-14 22:30 ` bugme-daemon
2008-12-14 23:10   ` Eric Sandeen
2008-12-15  1:22     ` Goswin von Brederlow
2008-12-14 23:10 ` bugme-daemon
2008-12-15  0:52 ` [Bug 12224] New: " Theodore Tso
2008-12-15  1:22 ` [Bug 12224] " bugme-daemon
2008-12-15  1:25 ` bugme-daemon
2008-12-15  2:47 ` bugme-daemon
2008-12-15  5:07 ` bugme-daemon
2008-12-15 21:49 ` bugme-daemon
2008-12-16 20:35 ` bugme-daemon
2008-12-16 22:01 ` bugme-daemon
2008-12-17  2:30 ` bugme-daemon [this message]
2008-12-18 19:56 ` bugme-daemon
2008-12-18 20:41 ` bugme-daemon
2008-12-18 23:02 ` bugme-daemon
2009-01-13 22:17 ` bugme-daemon
2009-01-14 20:35 ` bugme-daemon
2009-01-14 20:44 ` bugme-daemon
2009-01-14 22:37 ` bugme-daemon
2009-01-14 22:58 ` bugme-daemon
2009-01-15  1:09 ` bugme-daemon
2009-01-15 15:48 ` bugme-daemon
2009-01-15 16:12 ` bugme-daemon
2009-01-15 21:03 ` bugme-daemon
2009-02-23 12:22 ` bugme-daemon

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=20081217023008.54CF111D108@picon.linux-foundation.org \
    --to=bugme-daemon@bugzilla.kernel.org \
    --cc=linux-ext4@vger.kernel.org \
    /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;
as well as URLs for NNTP newsgroup(s).