Date: Sun, 03 Jun 2007 20:41:43 -0500 From: eculp@encontacto.net To: Garrett Cooper <youshi10@u.washington.edu> Cc: freebsd-current@freebsd.org Subject: Re: Couldn't build a release with this morning's sources md1 fixit floppy space problem. Message-ID: <20070603204143.mgpprab1dwos488c@intranet.encontacto.net> In-Reply-To: <4663369D.2020709@u.washington.edu> References: <20070603160628.usrmzygdkwooo40s@intranet.encontacto.net> <20070603163140.ihcy2jmpco84cw84@intranet.encontacto.net> <4663369D.2020709@u.washington.edu>
next in thread | previous in thread | raw e-mail | index | archive | help
Quoting Garrett Cooper <youshi10@u.washington.edu>: > eculp@encontacto.net wrote: >> Quoting eculp@encontacto.net: >> >>> I tried to build a release from this morning's sources and it =20 >>> seems that the fixit.flp needed more that the md alocated space. >>> >>> + [ x !=3D x ] >>> + mdconfig -a -t vnode -f /R/stage/floppies/fixit.flp >>> + MDDEVICE=3Dmd1 >>> + [ ! -c /dev/md1 ] >>> + trap umount /mnt; mdconfig -d -u md1 EXIT >>> + [ xbsdlabel !=3D x ] >>> + bsdlabel -w -B -b /R/stage/trees/base/boot/boot md1 fd1440 >>> + newfs -O1 -i 40000 -o space -m 0 /dev/md1c >>> /dev/md1c: 1.4MB (2880 sectors) block size 4096, fragment size 512 >>> using 2 cylinder groups of 1.22MB, 312 blks, 32 inodes. >>> super-block backups (for fsck -b #) at: >>> 32, 2528 >>> + mount /dev/md1c /mnt >>> + [ -d /R/stage/fixitfd ] >>> + set -e >>> + cd /R/stage/fixitfd >>> + + findcpio . -print -dump >>> /mnt >>> cpio: write error: No space left on device >>> + umount /mnt >>> + mdconfig -d -u md1 >>> *** Error code 1 >>> >>> Stop in /usr/src/release. >>> + umount /dev >>> *** Error code 1 >>> >>> I'm going to give it another try with MAKE_FLOPPIES=3Dfalse which =20 >>> will hopefully work. >>> >>> For future reference, it there a way to restart a broken make release? >> >> Maybe I could just have put a -DNO_CLEAN and MAKE_FLOPPIES=3Dfalse =20 >> after the error and continued but i have my doubts. Suggestions =20 >> apreciated. Especially being so near yet so far. >> >>> >>> ed > How large is it? Could it be the possible quadratic gcc 4.2 bug? > -Garrett > Darn, I already blew the release fs away [newfs] to try again with a =20 new cvsup. I'll check it this time, if the MAKE_FLOPPIES=3Dfalse =20 doesn't screw it up. sorry, ed
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20070603204143.mgpprab1dwos488c>