NetBSD-Bugs archive

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index][Old Index]

Re: port-sun2/56158: sun2 m68000: super-block backups (for fsck -b #) at: 32,nbmakefs: Writing inode 152 (work/./bin/cat), bytes 528384 + 4096: No space left on device



The following reply was made to PR port-sun2/56158; it has been noted by GNATS.

From: Jan-Benedict Glaw <jbglaw%lug-owl.de@localhost>
To: gnats-bugs%netbsd.org@localhost
Cc: cjep%netbsd.org@localhost, gnats-admin%netbsd.org@localhost, netbsd-bugs%netbsd.org@localhost
Subject: Re: port-sun2/56158: sun2 m68000: super-block backups (for fsck -b
 #) at: 32,nbmakefs: Writing inode 152 (work/./bin/cat), bytes 528384 + 4096:
 No space left on device
Date: Sat, 8 May 2021 21:59:54 +0200

 --wrorf5supk6zv6zm
 Content-Type: text/plain; charset=utf-8
 Content-Disposition: inline
 Content-Transfer-Encoding: quoted-printable
 
 On Sat, 2021-05-08 19:00:03 +0000, David Holland <dholland-bugs%netbsd.org@localhost>=
  wrote:
 >  On Sat, May 08, 2021 at 02:10:01PM +0000, jbglaw%lug-owl.de@localhost wrote:
 >   >  32,nbmakefs: Writing inode 152 (work/./bin/cat), bytes 528384 + 4096=
 : No space left on device
 > =20
 >  This means makefs thinks bin/cat is at least 528384 bytes long and
 >  likely longer. I assume it's crunchgen output, so being that size in
 >  the first place is not ridiculous, but ... I wonder if crunchgen
 >  broke.
 > =20
 >  You say you're doing toolchain tests but didn't say what you were
 >  testing...
 
 Toolchain testing was my starting point: I'm trying to regularly build
 a good number of cross-gcc configurations. With that setup running, I
 moved over to give further projects a run. NetBSD came to mind, so I
 did. Basically, fetching NetBSD trunk from the Github mirror (though
 that's a bit awkward as a plain "git pull" won't work too well) and
 then run:
 
 
 	./build.sh -U    -O "${OBJ_DIR}" -m "${BUILD_MACHINE}" -a "${BUILD_ARCH}" =
 tools
 	./build.sh -U -u -O "${OBJ_DIR}" -m "${BUILD_MACHINE}" -a "${BUILD_ARCH}" =
 release
 	./build.sh -U -u -O "${OBJ_DIR}" -m "${BUILD_MACHINE}" -a "${BUILD_ARCH}" =
 iso-image
 
 That's with $CC / $CXX being set/exported to Debian's "gcc-snapshot"
 binaries right now, could also use plain system gcc or clang.
 
   I'll re-test and monitor HDD consumption, but with > 100 GB free I
 rather guess that it's not my disk filling up, but a disk image. As
 I'm new into cross-building NetBSD, I might have done things quite
 wrong, but nothing obviously IMHO, so I decided to drop a bug report.
 
 MfG, JBG
 
 --=20
 
 --wrorf5supk6zv6zm
 Content-Type: application/pgp-signature; name="signature.asc"
 
 -----BEGIN PGP SIGNATURE-----
 
 iF0EABECAB0WIQQlDTvPcScNjKREqWEdvV51g5nhuwUCYJbttQAKCRAdvV51g5nh
 u/5tAJwKAJSxoLx1FEkbOTNLdzQ/gE1GEQCfRqGcCERxCCoHkb6frgCqUiTKJyQ=
 =ZyEA
 -----END PGP SIGNATURE-----
 
 --wrorf5supk6zv6zm--
 


Home | Main Index | Thread Index | Old Index