From: bugzilla@busybox.net
To: buildroot@uclibc.org
Subject: [Buildroot] [Bug 15436] New: qemu_s390x_defconfig: FS image too small
Date: Fri, 17 Mar 2023 17:02:24 +0000 [thread overview]
Message-ID: <bug-15436-163@https.bugs.busybox.net/> (raw)
https://bugs.busybox.net/show_bug.cgi?id=15436
Bug ID: 15436
Summary: qemu_s390x_defconfig: FS image too small
Product: buildroot
Version: unspecified
Hardware: All
OS: Linux
Status: NEW
Severity: normal
Priority: P5
Component: Other
Assignee: unassigned@buildroot.uclibc.org
Reporter: jbglaw@lug-owl.de
CC: buildroot@uclibc.org
Target Milestone: ---
The qemu_s390x_defconfig configuration suffers from a too small FS image:
[build 2023-03-16 06:10:06] mke2fs 1.46.5 (30-Dec-2021)
[build 2023-03-16 06:10:06] Creating regular file
/var/lib/laminar/run/buildroot-qemu_s390x_defconfig/1/buildroot/output/images/rootfs.ext2
[build 2023-03-16 06:10:06] Creating filesystem with 61440 1k blocks and 15360
inodes
[build 2023-03-16 06:10:06] Filesystem UUID:
ec8acc08-401f-448b-a2eb-b95481434d6a
[build 2023-03-16 06:10:06] Superblock backups stored on blocks:
[build 2023-03-16 06:10:06] 8193, 24577, 40961, 57345
[build 2023-03-16 06:10:06]
[build 2023-03-16 06:10:06] Allocating group tables: done
[build 2023-03-16 06:10:06] Writing inode tables: done
[build 2023-03-16 06:10:06] Copying files into the device: __populate_fs: Could
not allocate block in ext2 filesystem while writing file "ata_id"
[build 2023-03-16 06:10:06] mkfs.ext2: Could not allocate block in ext2
filesystem while populating file system
[build 2023-03-16 06:10:06] *** Maybe you need to increase the filesystem size
(BR2_TARGET_ROOTFS_EXT2_SIZE)
[build 2023-03-16 06:10:06] make: *** [fs/ext2/ext2.mk:66:
/var/lib/laminar/run/buildroot-qemu_s390x_defconfig/1/buildroot/output/images/rootfs.ext2]
Error 1
Full build log at
http://toolchain.lug-owl.de/laminar/log/buildroot-qemu_s390x_defconfig/1
--
You are receiving this mail because:
You are on the CC list for the bug.
_______________________________________________
buildroot mailing list
buildroot@buildroot.org
https://lists.buildroot.org/mailman/listinfo/buildroot
reply other threads:[~2023-03-17 17:02 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=bug-15436-163@https.bugs.busybox.net/ \
--to=bugzilla@busybox.net \
--cc=buildroot@uclibc.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).