On Feb 05, 2004 12:00 -0500, Eric Wood wrote: > Our Invoice posting routine (intensive harddrive io) freezes every few > seconds to flush the cache. Reading this: > > https://listman.redhat.com/archives/ext3-users/2002-November/msg00070.html > > > I decided to try: > > # elvtune -r 2048 -w 131072 /dev/sda > # echo "90 500 0 0 600000 600000 95 20 0" >/proc/sys/vm/bdflush > # run_post_routine > # elvtune -r 128 -w 512 /dev/sda > # echo "30 500 0 0 500 3000 60 20 0" >/proc/sys/vm/bdflush > # sync > > I like it, but I think that's way too lax and risky - the whole post routine > never wrote to disk until I sync'd! But, is there a setting that would > ensure reliable constant i/o so that my post process is pretty much all > flushed in real time? Is constantly changing the bdflush parameters before > the type of job I'm about to run a bad thing? I noticed that changing back > to the "30 500 0 0 500 3000 60 20 0" default doesn't flush to queue, I still > had to "sync". You could try deleting the journal and creating a larger one (unmounted!): tune2fs -O ^has_journal <dev> tune2fs -J size=128 <dev> Max journal size is 400MB, but this can also consume that much RAM so use with caution. Cheers, Andreas -- Andreas Dilger http://sourceforge.net/projects/ext2resize/ http://www-mddsp.enel.ucalgary.ca/People/adilger/ _______________________________________________ Ext3-users@xxxxxxxxxx https://www.redhat.com/mailman/listinfo/ext3-users
