2 May
2003
2 May
'03
5:02 p.m.
mark,
actually, the idea is to get my jack running with --realtime
capabilities w/o a system freeze due to kernel 2.4.20 + ext3 problems.
this will hopefully fix my xrun difficulties. but what you said makes
sense, so i changed the fs of my root partition from ext3 to ext2 in the
/etc/fstab and rebooted. guess what? it still mounted as ext3! why is
that?!? just to make sure, i issued a "jackstart --realtime -d alsa -d
hw", and guess what else? the system froze, just like it should.
is there another way to mount my root partition as ext2? ...last chance
before everything gets converted! :-)
and... how would one change the journalling commit time, anyway? another
thing you mention in the 'xruns vs disk activity thread' is turning off
chrond... can you elaborate on that as well, pls?
best,
d.
Mark Knecht wrote:
If the idea here is that the xruns are caused by the
ext3 journaling
operations, wouldn't a simple test be to mount the ext3 partition as ext2
and prove it before doing all the work to move to reiserfs only to find out
it's something else? Or possibly change the journaling commit time to reduce
or increase the xruns?