On Wed, Dec 12, 2001 at 11:06:26AM +0000, Theo wrote: > Question that comes naturally to my mind is if you have build JFS as part of > the kernel (not a module) what the result would be then ? > > Just to verify you race condition, will it help if you insert the > line "insmod /lib/modules/xxxx/xxxx/jfs.o" (I'm not sure if the syntax) at the > beginning of the rc.sysinit. >
If you put the jfs.o into the initrd.img it'll load way before the rc.sysinit does. Use mkinitrd and pass it the --with=jfs option. See the mkinitrd man page for details. Don't for get to run lilo and include the initrd image with the kernel. Of course, you don't need to do this if your jfs is built into the kernel rather than a module. -- Scott > > yikes following up to self 2x :-( > > > > I've at least found a work-around, still a bit confused about why > > this is happening. - At Theo's suggestion, I added the line > > > > touch /var/testfile to etc/rc.d/rc.sysinit > > > > On booting after a crash, this generated a "no space left on device" > > error message. > > > > The hack to get operational was simply to add a couple of 'sync' > > commands after fsck.jfs has been run. > > > > The offending line in /etc/rc.d/rc.sysinit is presumably > > > > ca. line 612: >/var/run/utmp > > > > I suppose it could also be a simple timing problem, although linux > > sync(2) is *supposed* to guarantee that writes have occured, or > > does fsck.jfs not call sync(2)? .. I doubt timing is the issue, as > > several seconds have passed from the time that fsck was run until > > the lockup. > > -- Regards, Scott Russell ([EMAIL PROTECTED]) Linux Technology Center, System Admin, RHCE. T/L 441-9289 / External 919-543-9289 http://bzimage.raleigh.ibm.com/webcam _______________________________________________ Jfs-discussion mailing list [EMAIL PROTECTED] http://www-124.ibm.com/developerworks/oss/mailman/listinfo/jfs-discussion
