Date: Fri, 18 Aug 2023 20:46:52 +0200 From: Matthias Apitz <guru@unixarea.de> To: freebsd-current@freebsd.org Subject: Re: make-memstick.sh creates in 14.0-CURRENT run-away processes Message-ID: <ZN%2B8nOjERrCdzfx0@c720-r368166> In-Reply-To: <ZN%2BZpl4Rnq9lnv7A@c720-r368166> References: <ZN%2BZpl4Rnq9lnv7A@c720-r368166>
next in thread | previous in thread | raw e-mail | index | archive | help
I filed this PR: https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=273211 about the issue. El día viernes, agosto 18, 2023 a las 06:17:42p. m. +0200, Matthias Apitz escribió: > > I was used to use in 13.0-CURRENT the script "make-memstick.sh" to > create memstick immages to install the system on smaller devices where > the OS can't build from the sources, and it always worked fine for many > years. Now I'm ready to do so with my fresh compiled system (sources > from git August, 5: > > $ uname -a > FreeBSD jet 14.0-CURRENT FreeBSD 14.0-CURRENT amd64 1400094 #0 main-n264568-1d7ffb373c9d: Sat Aug 5 17:22:47 CEST 2023 guru@jet:/usr/obj/usr/src/amd64.amd64/sys/GENERIC amd64 > > but the image is not produces and some processes create temp > files of 800++ GByte. Here are the details: > > root@jet:/usr/src/release/amd64 # ./make-memstick.sh /home/guru/140.root ~guru/memstick.img > Calculated size of `/home/guru/memstick.img.part': 23795073024 bytes, 263113 inodes > Extent size set to 32768 > /home/guru/memstick.img.part: 22692.8MB (46474752 sectors) block size 32768, fragment size 4096 > using 27 cylinder groups of 869.44MB, 27822 blks, 10240 inodes. > super-block backups (for fsck -b #) at: > 192, 1780800, 3561408, 5342016, 7122624, 8903232, 10683840, > 12464448, 14245056, 16025664, 17806272, 19586880, 21367488, 23148096, > 24928704, 26709312, 28489920, 30270528, 32051136, 33831744, 35612352, > 37392960, 39173568, 40954176, 42734784, 44515392, 46296000 > Populating `/home/guru/memstick.img.part' > Image `/home/guru/memstick.img.part' complete > Creating `/tmp/efiboot.iFachZ' > /tmp/efiboot.iFachZ: 65528 sectors in 65528 FAT32 clusters (512 bytes/cluster) > BytesPerSec=512 SecPerClust=1 ResSectors=32 FATs=2 Media=0xf0 SecPerTrack=63 Heads=255 HiddenSecs=0 HugeSectors=66584 FATsecs=512 RootCluster=2 FSInfo=1 Backup=2 > Populating `/tmp/efiboot.iFachZ' > Image `/tmp/efiboot.iFachZ' complete > > It says 'complete' but never ends growing the file /tmp/mkimg-oGNnFb: > > root@jet:/usr/home/guru # ls -ltrah /tmp | tail -6 > drwx------ 2 guru wheel 512B Aug 18 15:43 tmux-1001 > -rw------- 1 root wheel 33M Aug 18 17:18 efiboot.iFachZ > -rw------- 1 root wheel 0B Aug 18 17:18 mkimg-4eMWKW > drwxrwxrwt 21 root wheel 1.0K Aug 18 17:18 . > drwxr-xr-x 22 root wheel 1.0K Aug 18 17:43 .. > -rw------- 1 root wheel 850G Aug 18 17:53 mkimg-oGNnFb > > root@jet:/usr/home/guru # ls -ltrh mem* > -rw-r--r-- 1 root wheel 22G Aug 18 17:18 memstick.img.part > -rw-r--r-- 1 root wheel 0B Aug 18 17:18 memstick.img > > Only a hard reset and reboot helps. > > What does it mean? > > matthias > > > -- > Matthias Apitz, ✉ guru@unixarea.de, http://www.unixarea.de/ +49-176-38902045 > Public GnuPG key: http://www.unixarea.de/key.pub > -- Matthias Apitz, ✉ guru@unixarea.de, http://www.unixarea.de/ +49-176-38902045 Public GnuPG key: http://www.unixarea.de/key.pub
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?ZN%2B8nOjERrCdzfx0>