> Is this problem repeatable? Yes, as per my original e-mail, it has happened twice already. The first time the last command in the build log was very similar, but involved a different object file. The perl-process was stuck as "running" and I was able to kill it, but the subsequent `rm -rf work' became unkillable in "ufs", just like `find' is now. > What does "ps lax" say about the hung processes? 0 65327 8694 0 -4 0 1432 908 ufs D+ p2 0:02,05 find work/ -name provider.o > Where is the reboot sequence did the system hang? Don't remember -- well after shutting syslogd. Presumably -- while trying to umount everything. > What problems did fsck fix? Oct 3 21:03:12 roo fsck: /dev/da0s2e: ZERO LENGTH DIR I=325352 OWNER=mi MODE=42755 Oct 3 21:03:12 roo fsck: /dev/da0s2e: SIZE=0 MTIME=Oct 3 11:22 2005 (CLEARED) Oct 3 21:03:12 roo fsck: /dev/da0s2e: Reclaimed: 0 directories, -2 files, -37 fragments Oct 3 21:03:12 roo fsck: /dev/da0s2e: 364942 files, 1204019 used, 2386729 free (79873 frags, 288357 blocks, 2.2% fragmentation) > My RELENG_6 box doesn't have enough space to build OOo, but I can try it > on HEAD, which should be very similar. Thank you! -miReceived on Tue Oct 04 2005 - 14:56:14 UTC
This archive was generated by hypermail 2.4.0 : Wed May 19 2021 - 11:38:44 UTC