Date: Fri, 18 May 2001 21:25:59 -0700 (PDT) From: David Wolfskill <david@catwhisker.org> To: current@FreeBSD.ORG Subject: Re: Panic during -CURRENT buildworld Message-ID: <200105190425.f4J4PxM89679@bunrab.catwhisker.org> In-Reply-To: <200105181748.f4IHmJS88409@bunrab.catwhisker.org>
next in thread | previous in thread | raw e-mail | index | archive | help
>Date: Fri, 18 May 2001 10:48:19 -0700 (PDT) >From: David Wolfskill <david@catwhisker.org> >[Excruciatingly long narrative of panic during buildworld for today's -CURRENT elided; it's in the archives. dhw] Reporting back after getting today's -CURRENT built: FreeBSD dhcp-140.catwhisker.org 5.0-CURRENT FreeBSD 5.0-CURRENT #2: Fri May 18 11:31:46 PDT 2001 root@:/common/C/obj/usr/src/sys/LAPTOP_30W i386 Taking a cue from Szilveszter Adam's response to my note, I booted into single-user mode, turned off soft updates for the file systems on ad0s3 (all of which get used during the biuldworld/installworld process, since /usr/obj is a symlink to somwhere in /common -- df listing below for reference), and I unmounted the file systems on ad0s1 & ad0s2. I then did the make buildworld/kernel/installworld & mergemaster while remaining in single-user mode, running yesterday's -CURRENT (but, as noted, with soft updates turned off for all mounted file systems). As noted, it appears to have completed successfully. I have turned soft updates back on for everything. Tomorrow's build may prove "interesting". Here's what "df -k" looks like (while I'm running -CURRENT): Filesystem 1K-blocks Used Avail Capacity Mounted on /dev/ad0s3a 95263 73782 13860 84% / devfs 1 1 0 100% /dev /dev/ad0s1a 95263 40812 46830 47% /S1 /dev/ad0s1e 915695 777472 64968 92% /S1/usr /dev/ad0s2a 95263 41030 46612 47% /S2 /dev/ad0s2e 915727 776108 66361 92% /S2/usr /dev/ad0s3e 915727 733431 109038 87% /usr /dev/ad0s3g 254063 107557 126181 46% /var /dev/ad0s3h 14116697 4180188 8807174 32% /common procfs 4 4 0 100% /proc /dev/md10c 520140 16 478516 0% /tmp I haven't seen anyone else reporting any problems similar to what I experienced, so I'm not about to claim there's something that's definitely broken.... Cheers, david -- David H. Wolfskill david@catwhisker.org As a computing professional, I believe it would be unethical for me to advise, recommend, or support the use (save possibly for personal amusement) of any product that is or depends on any Microsoft product. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?200105190425.f4J4PxM89679>