I've been running 3.0.0-19990112-SNAP for about half the weekend now and have run into the same problem twice while having several compile windows open. Both happened after I turned on softupdates on both my partitions (I have a / partition + swap on my first IDE drive, and a /usr partition on my second.)
The system becomes totally unresponsive (console driver still seems to be running but the processes all seem to have hung) at some random point. The second time, I noticed my second hard drive was going totally crazy -- sounded like a `find /' or something. :) In both cases, I couldn't Ctrl-Alt-Del, so I rebooted. The first time, I didn't know what to expect -- but the standard fsck-if-not-clean "took care" of my problem on reboot. I didn't get to see many of the messages, but I did catch quite a few (and on the tail) clearing of unref files, many owned by me. They seemed to (and indeed did) correspond to some files that I was unpacking. Attributing it to just running into a random bug, I re-unpacked the files and went on. Several kernel recompiles later (I've noticed it takes a *lot* less time to recompile a kernel after a compile directory already exists, even though I'm running config each time... I take it 3.0's config doesn't clear the compile directory beforehand?), it happened again -- just a little while ago. I rebooted into single user and fsck -p'd both partitions, which proceeded to display quite a large number of incorrect block counts (most along the line of `12 should be 0' or something very similar), followed by the expected glob of unref files, and then it pronounced the filesystems clean. Just to make sure, I turned off softupdates for now, and am running all mounts sync again. (Especially since tomorrow I won't be around to flip the power if I need to.) Any ideas on what I should do? Should I, perhaps, make sure kernel compile directories are cleared all the time and the like? Or maybe I should just stick to sync, seeing as how I've got only 32M of real RAM? I was reading through the softupdates README and thought maybe it might have to do with hitting that `wall' and suddenly having to dump a very large amount of stuff to disk. In any case, it doesn't seem to be wiping stuff out that I haven't written to in that session, so I suppose I'm lucky. :) - Matt Behrens <m...@zigg.com> Network Administrator, zigg.com <http://www.zigg.com/> Engineer, Nameless IRC Network <http://www.nameless.net/> To Unsubscribe: send mail to majord...@freebsd.org with "unsubscribe freebsd-current" in the body of the message
