Skip to contentSkip to conversation

tracking down disk spinups.

DISCUSSION Dave Jones 5 participants 11 messages May 14, 2007 – May 15, 2007

lore
Share & tools
lore

Dave Jones

author
#0 lore raw

I was curious why my firewall box never spins down its disk. Given it rarely writes stuff to logs, it's odd that it always seems to have something to write out.
killing syslogd, and enabling /proc/sys/vm/block_dump gets me a periodic spew in /proc/kmsg like..

<7>[2695397.990000] kjournald(366): WRITE block 243056 on dm-0
<7>[2695397.990000] kjournald(366): WRITE block 243064 on dm-0
<7>[2695397.990000] kjournald(366): WRITE block 243072 on dm-0
<7>[2695397.990000] kjournald(366): WRITE block 243080 on dm-0

How do I map those blocks back to files ?
I tried mapping these from blocks->inodes->names using debugfs but that doesn't get me very far..

debugfs: icheck 243056
Block Inode number
243056 <block not found>

Given the dirtying process name is kinda useless, I wondered if I'd get something more useful if I used ext2 instead of ext3, when I found this oddness..

(14:49:52:root@firewall:~)# mount
/dev/mapper/VolGroup00-LogVol00 on / type ext3 (rw)
(14:49:56:root@firewall:~)# mount /dev/mapper/VolGroup00-LogVol00 / -t ext2 -o remount,rw
(14:50:37:root@firewall:~)# mount
/dev/mapper/VolGroup00-LogVol00 on / type ext3 (rw)

Why did the kernel ignore what I told it to do ? I'm sure it thinks it knows better than me for a reason, but I'd like to know what it is.

Dave

Signature · 1 line
http://www.codemonkey.org.uk
#1 lore raw
Quoted 9 lines · Dave Jones
(14:49:52:root@firewall:~)# mount
/dev/mapper/VolGroup00-LogVol00 on / type ext3 (rw)
(14:49:56:root@firewall:~)# mount /dev/mapper/VolGroup00-LogVol00 / -t ext2 -o remount,rw
(14:50:37:root@firewall:~)# mount
/dev/mapper/VolGroup00-LogVol00 on / type ext3 (rw)

Why did the kernel ignore what I told it to do ? I'm sure it thinks it knows better than me for a reason, but I'd like to know what it is.

Are you sure it's the kernel, and not just mount ? Did you try cat /proc/mounts ?

Xav

author
#2 lore raw
Quoted 8 lines · Xavier Bestel
Quoted 6 lines · Dave Jones
(14:49:52:root@firewall:~)# mount
/dev/mapper/VolGroup00-LogVol00 on / type ext3 (rw)
(14:49:56:root@firewall:~)# mount /dev/mapper/VolGroup00-LogVol00 / -t ext2 -o remount,rw
(14:50:37:root@firewall:~)# mount
/dev/mapper/VolGroup00-LogVol00 on / type ext3 (rw)
Quoted 6 lines
Quoted 3 lines

Why did the kernel ignore what I told it to do ? I'm sure it thinks it knows better than me for a reason, but I'd like to know what it is.

Are you sure it's the kernel, and not just mount ? Did you try cat /proc/mounts ?

Yes. It's further evidenced that it's ext3 by the fact that kjournald still shows up in the logs.
Not a single line gets printed to dmesg.

Dave

Signature · 1 line
http://www.codemonkey.org.uk
#3 lore raw
In reply to Dave Jones
Quoted 10 lines · Dave Jones
(14:49:52:root@firewall:~)# mount
/dev/mapper/VolGroup00-LogVol00 on / type ext3 (rw)
(14:49:56:root@firewall:~)# mount /dev/mapper/VolGroup00-LogVol00 / -t ext2 -o remount,rw
(14:50:37:root@firewall:~)# mount
/dev/mapper/VolGroup00-LogVol00 on / type ext3 (rw)

Why did the kernel ignore what I told it to do ? I'm sure it thinks it knows better than me for a reason, but I'd like to know what it is.

I don't think you can change filesystem types with remount. Doesn't that just change flags on an existing mount?

J

#4 lore raw
Quoted 2 lines · Jeremy Fitzhardinge

I don't think you can change filesystem types with remount. Doesn't that just change flags on an existing mount?

+1

#5 lore raw
Quoted 5 lines · Xavier Bestel
Quoted 2 lines · Jeremy Fitzhardinge

I don't think you can change filesystem types with remount. Doesn't that just change flags on an existing mount?

+1

+2.

Hell, it'd be fun to switch from reiser to xfs by just passing in a -t!

Jan

#6 lore raw
In reply to Dave Jones
Quoted 6 lines · Dave Jones

I was curious why my firewall box never spins down its disk. Given it rarely writes stuff to logs, it's odd that it always seems to have something to write out.
killing syslogd, and enabling /proc/sys/vm/block_dump gets me a periodic spew in /proc/kmsg like..

Perhaps it would help if you use fuser to see who's got open files for read and/or write, then strace all processes and see who does reads/writes?

Jan

#7 lore raw
In reply to Dave Jones
Quoted 3 lines · Dave Jones

Why did the kernel ignore what I told it to do ? I'm sure it thinks it knows better than me for a reason, but I'd like to know what it is.

Remount doesn't switch filesystem drivers, it tells the existing filesystem driver to accept new flags and/or a new option string.

To switch drivers you have to umount the old sucker and mount the new one. (The idea of handing off consistent cache data from one mounted filesystem driver to another... Ouch.)

Most filesystem drivers aren't compatible with each other anyway. Sounds like what you really want to do is put the ext3 driver into "ext2 mode", and stop journaling. Many people have wanted this over the years, but alas our dream of "one darn driver for the ext# family" got squashed years ago because people wanted two different codebases for the same filesystem that could diverge, require the same bugs to be fixed twice, become incompatible...

Rob

author
#8 lore raw
Quoted 7 lines · Rob Landley
Quoted 3 lines · Dave Jones

Why did the kernel ignore what I told it to do ? I'm sure it thinks it knows better than me for a reason, but I'd like to know what it is.

Remount doesn't switch filesystem drivers, it tells the existing filesystem driver to accept new flags and/or a new option string.

yes, I had misinterpreted what 'remount' did. I thought behind the scenes it actually did a umount/mount.

Quoted 3 lines

To switch drivers you have to umount the old sucker and mount the new one. (The idea of handing off consistent cache data from one mounted filesystem driver to another... Ouch.)

a umount would purge the cache, but that's irrelevant given it doesn't work that way.

Anyways, I rebooted after s/ext3/ext2/ on my fstab, and found things hadn't really got any more obvious what was going on. Instead of 'kjournald' writing stuff out, now it's 'pdflush'.

*has sudden brainwave*

Ahh, it's doing atime updates. Duh.

Dave

Signature · 1 line
http://www.codemonkey.org.uk
#9 lore raw
Quoted 4 lines · Dave Jones

*has sudden brainwave*

Ahh, it's doing atime updates. Duh.

FYI+, noatime,nodiratime :)

Jan

#10 lore raw
In reply to Dave Jones
Quoted 7 lines · Dave Jones
Quoted 6 lines · Rob Landley
Quoted 3 lines · Dave Jones

Why did the kernel ignore what I told it to do ? I'm sure it thinks it knows better than me for a reason, but I'd like to know what it is.

Remount doesn't switch filesystem drivers, it tells the existing

filesystem

Quoted 4 lines
Quoted 1 line

driver to accept new flags and/or a new option string.

yes, I had misinterpreted what 'remount' did. I thought behind the scenes it actually did a umount/mount.

I implemented the BusyBox mount command last year. (Well, rewrote three times until just about none of the old code was left.) Getting remount to work right is a monster headache. (The new flags _replace_ the old flags, not delta against them, so you have to parse /etc/mtab (or /proc/mounts), read the old flags out of that, mask them yourself, and supply them back in. And of course, not all of them are flags, some remain strings, but you can't keep strings you turned into flags because the driver will barf that it's an unrecognized string option... Headache. And don't get me started on vfat spitting back string options from /proc/mounts that are THE DEFAULT VALUES... Grrr. I'll stop now.)

You can always umount/mount yourself.

Quoted 1 line
Quoted 1 line

To switch drivers you have to umount the old sucker and mount the new

one.

Quoted 1 line
Quoted 1 line

(The idea of handing off consistent cache data from one mounted

filesystem

Quoted 5 lines
Quoted 1 line

driver to another... Ouch.)

a umount would purge the cache, but that's irrelevant given it doesn't work that way.

Quoted 7 lines

Anyways, I rebooted after s/ext3/ext2/ on my fstab, and found things hadn't really got any more obvious what was going on. Instead of 'kjournald' writing stuff out, now it's 'pdflush'.

*has sudden brainwave*

Ahh, it's doing atime updates. Duh.

I had to add MS_SILENT (1<<15) to the default mount options for busybox (because otherwise the kernel got log message diarrhea). I was seriously tempted to add MS_NOATIME to that, but didn't.

I should write up a good "mount" spec, from the kernel's point of view. (There isn't one. I looked.)

Rob