Can't think why you had to remove the quotaon from the sysinit file, should
only needed to remove the quota entry from the /etc/fstab file. How
does /etc/fstab looks ?
Try adding something like "touch /var/testfile" in the sysinit file. At least
you will know that can create an empty file or not.
If you can mount the jfs /var in single-user mode and you are sure that there
is enought space on the jfs /var, then I'm running out of ideas.
Theo
> Failed boot again, having removed the quotaon line from /etc/rc.d/rc.sysinit,
> IO'm pretty sure that wasn't the problem.
>
> Here's the circs that cause the failure
>
> - prior crash
> i.e. my / and /boot filesystems have just undergone fsck
> Note: these are still ext2fs format
>
> on one boot failure the console popped up a message that
> a file could not be written to /var/run/.... -no space left on device
>
> The set of code following the quotas message squares with this
>
> Any ideas why it fails only after a crash???? the only things I
> can think of that would affect the post-crash situation are:
>
>
> the / & /boot filesystems have just been fsck'd
>
> Some files on jfs-formatted /var were not properly closed, and in spite
> of boot-time fsck / log replay , they hang in the code that's posted below
>
>
> Any ideas from what follows here?
>
> Hoping for some ideas *before* I start metering this & intentionally
> crashing to find the spot that's hanging
>
>
> --- Excerpted from rc.sysinit
>
> # Clean out /etc.
> rm -f /fastboot /fsckoptions /forcefsck /halt /poweroff
>
> # Do we need (w|u)tmpx files? We don't set them up, but the sysadmin might...
> _NEED_XFILES=
> [ -f /var/run/utmpx -o -f /var/log/wtmpx ] && _NEED_XFILES=1
>
> # Clean up /var
> # I'd use find, but /usr may not be mounted.
> for afile in /var/lock/* /var/run/*; do
> if [ -d "$afile" ]; then
> [ "`basename $afile`" != "news" -a "`basename $afile`" != "sudo" -a
> "`basename $afile`" != "mon" ] && rm -f $afile/*
> else
> rm -f $afile
> fi
> done
>
> # Reset pam_console permissions
> [ -x /sbin/pam_console_apply ] && /sbin/pam_console_apply -r
>
> {
> # Clean up utmp/wtmp
> >/var/run/utmp
> touch /var/log/wtmp
> chgrp utmp /var/run/utmp /var/log/wtmp
> chmod 0664 /var/run/utmp /var/log/wtmp
> if [ -n "$_NEED_XFILES" ]; then
> >/var/run/utmpx
> touch /var/log/wtmpx
> chgrp utmp /var/run/utmpx /var/log/wtmpx
> chmod 0664 /var/run/utmpx /var/log/wtmpx
> fi
>
> --- end Excerpt
>
>
>
>
>
>
>
>
> On Fri, 7 Dec 2001 09:33:32 -0500
> forrest whitcher <[EMAIL PROTECTED]> forrest whitcher did inscribe thusly:
>
> >
> > I got a clean boot just now - problem is I didn't do anything between
> > 2 successive reboots - however I had figured that quotacheck - hanging
> > was the problem and had begun disableing quotas
> >
> > Thanks, for now I seem to be go-ready
> >
> > now for the /root & /boot partitions :-)
> >
> > forrest
> >
> > On Fri, 7 Dec 2001 07:24:20 GMT
> > Theo <[EMAIL PROTECTED]> Theo did inscribe thusly:
> >
> > > If I'm not wrong then Quotas are not yet implemented in JFS.
> > >
> > > Theo
> > >
> > > >
> > > > evening all,
> > > >
> > > > I've just been installing JFS (drop 1.0.10 on a thinkpad -t23 linux
2.4.12
> > > >
> > > > everything was running well (copy/reformat user filesystems as JFS,
reboot
> > > > all's ok. Then the /usr /var while in maint mode.
> > > >
> > > > On reboot, however the boot sequence is now hanging on:\
> > > >
> > > > "Turning on user and group quotas for local filesystems" [ OK ]
> > > >
> > > > It either hangs right there or puts up one more messages saying
(roughly)
> > > >
> > > > no space left on device /var/run/<mumble>
> > > >
> > > > the fs I'm using for /var mounts ok and looks good in all other
> > > > respects. - one oddity, all the other FS's report only 'Phase 0'
> > > > this one (on one reboot only( reported all phases up to "Phase 8"
> > > >
> > > > Any thoughts on this appreciated, I left copies of all the system
> > > > partitions on a temp partition ext2/formated so I have a spare
> > > > /var, but I can't think why this shouldn't be working?
> > > >
> > > > forrest
> > > > _______________________________________________
> > > > Jfs-discussion mailing list
> > > > [EMAIL PROTECTED]
> > > > http://www-124.ibm.com/developerworks/oss/mailman/listinfo/jfs-
discussion
> > >
> > >
> > > ---------------------------------------------
> > > This message was sent using M-Web Airmail.
> > > http://airmail.mweb.co.za/
> > >
> > >
> > > _______________________________________________
> > > Jfs-discussion mailing list
> > > [EMAIL PROTECTED]
> > > http://www-124.ibm.com/developerworks/oss/mailman/listinfo/jfs-discussion
> > _______________________________________________
> > Jfs-discussion mailing list
> > [EMAIL PROTECTED]
> > http://www-124.ibm.com/developerworks/oss/mailman/listinfo/jfs-discussion
> _______________________________________________
> Jfs-discussion mailing list
> [EMAIL PROTECTED]
> http://www-124.ibm.com/developerworks/oss/mailman/listinfo/jfs-discussion
---------------------------------------------
This message was sent using M-Web Airmail.
http://airmail.mweb.co.za/
_______________________________________________
Jfs-discussion mailing list
[EMAIL PROTECTED]
http://www-124.ibm.com/developerworks/oss/mailman/listinfo/jfs-discussion
