![]() | |
![]() |
| | Thread Tools | Display Modes |
#1
| |||
| |||
|
#2
| |||
| |||
|
|
Oh, BTW, if you don't want to reinstall and reformat for ext2: 1) stop D3 and anything else that may read/write on the partitions 2) sync and unmount the partitions 3) tune2fs -O ^has_journal /dev/<partition 4) remount the partitions Result: you no longer have journaling ^has_journal disables journaling on existing ext3/2 file systems. ext2 and ext3 are the same FS, except ext3 has optional feature bits set in the superblock. Check out the other -O options in 'man tune2fs'. A carat preceding an option turns it off. Glen "bruce ackman" <lewissupply (AT) copper (DOT) net> wrote in message news:45769feb_5 (AT) newsfeed (DOT) slurp.net... I recently upgraded to a new server, still running RedHat9 and D3. I set up all the partitions as ext3. I'm getting constant messages about "Sytem CPU (XX%) exceeds 25%". When I run top at the Linux prompt, kjournald is always the culprit. Since I only run D3 and Vsifax, and Vsifax is not that busy an application, I wonder if kjournald is runing on the unmounted D3 partitions. Last time I shutdown D3, kjournald dropped to almost no CPU usage. Does anyone else have this problem? Should I shutdown D3 and convert the filesytems to ext2? I tried adding the noatime option to the mounted systems in /etc/fstab, but that didn't help at all. Thanks, Bruce |
#3
| |||
| |||
|
|
Oh, BTW, if you don't want to reinstall and reformat for ext2: 1) stop D3 and anything else that may read/write on the partitions 2) sync and unmount the partitions 3) tune2fs -O ^has_journal /dev/<partition 4) remount the partitions Result: you no longer have journaling ^has_journal disables journaling on existing ext3/2 file systems. ext2 and ext3 are the same FS, except ext3 has optional feature bits set in the superblock. Check out the other -O options in 'man tune2fs'. A carat preceding an option turns it off. Glen "bruce ackman" <lewissupply (AT) copper (DOT) net> wrote in message news:45769feb_5 (AT) newsfeed (DOT) slurp.net... I recently upgraded to a new server, still running RedHat9 and D3. I set up all the partitions as ext3. I'm getting constant messages about "Sytem CPU (XX%) exceeds 25%". When I run top at the Linux prompt, kjournald is always the culprit. Since I only run D3 and Vsifax, and Vsifax is not that busy an application, I wonder if kjournald is runing on the unmounted D3 partitions. Last time I shutdown D3, kjournald dropped to almost no CPU usage. Does anyone else have this problem? Should I shutdown D3 and convert the filesytems to ext2? I tried adding the noatime option to the mounted systems in /etc/fstab, but that didn't help at all. Thanks, Bruce |
![]() |
| Thread Tools | |
| Display Modes | |
| |