http://bugzilla.kernel.org/show_bug.cgi?id=12224 ------- Comment #10 from csights@xxxxxxxxxxx 2008-12-16 18:30 ------- On Tuesday 16 December 2008 17:01:27 bugme-daemon@xxxxxxxxxxxxxxxxxxx wrote: > http://bugzilla.kernel.org/show_bug.cgi?id=12224 > ------- Comment #9 from sandeen@xxxxxxxxxx 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. -- To unsubscribe from this list: send the line "unsubscribe linux-ext4" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
