dbTalk Databases Forums  

d3/linux & ext3 partitions - a problem?

comp.databases.pick comp.databases.pick


Discuss d3/linux & ext3 partitions - a problem? in the comp.databases.pick forum.



Reply
 
Thread Tools Display Modes
  #1  
Old   
bruce ackman
 
Posts: n/a

Default d3/linux & ext3 partitions - a problem? - 12-06-2006 , 08:22 AM






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

Reply With Quote
  #2  
Old   
bruce ackman
 
Posts: n/a

Default Re: d3/linux & ext3 partitions - a problem? - 12-07-2006 , 11:29 AM






Thank you,

I'd already looked up how to convert ext3 to ext2. I am suffering an
unbelievable performance hit, I was just worried about having to
reinstall from a backup if I made the change.

Bruce

Glen B wrote:
Quote:
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




Reply With Quote
  #3  
Old   
bruce ackman
 
Posts: n/a

Default Re: d3/linux & ext3 partitions - a problem? - 12-07-2006 , 04:47 PM



tune2fs gave me error messages

bad magic number in superblock
couldn't find valid filesystem superblock

I tried the -f option with the same results.

Looks like I'll have to wait 'til this weekend. I'll delete and
recreate the partitions and then do a file-restore. Unless someone has
another idea?

Bruce

Glen B wrote:
Quote:
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




Reply With Quote
Reply




Thread Tools
Display Modes

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

vB code is On
Smilies are On
[IMG] code is On
HTML code is Off



Powered by vBulletin Version 3.5.3
Copyright ©2000 - 2012, Jelsoft Enterprises Ltd.