From: bugzilla at busybox.net <bugzilla@busybox.net>
To: buildroot@busybox.net
Subject: [Buildroot] [Bug 8831] New: image generation fails on host ZFS due to "no free space"
Date: Tue, 29 Mar 2016 21:01:34 +0000 [thread overview]
Message-ID: <bug-8831-163@https.bugs.busybox.net/> (raw)
https://bugs.busybox.net/show_bug.cgi?id=8831
Bug ID: 8831
Host: raspberrypi2
Build: amd64 Debian GNU/Linux jessie with ZFS on Linux
Summary: image generation fails on host ZFS due to "no free
space"
Product: buildroot
Version: unspecified
Hardware: All
OS: Linux
Status: NEW
Severity: normal
Priority: P5
Component: Other
Assignee: unassigned at buildroot.uclibc.org
Reporter: post at lespocky.de
CC: buildroot at uclibc.org
Target Milestone: ---
Created attachment 6411
--> https://bugs.busybox.net/attachment.cgi?id=6411&action=edit
last output
I tried building master at 4a6602f77cfe429d1dfc4f36964240b7d4410c54 today with
only http://patchwork.ozlabs.org/patch/602668/ applied on top. The steps I did:
`make distclean`
`make raspberrypi2_defconfig`
`make menuconfig`
activate dropbear with default options
`make`
Build fails with genext2fs not being able to allocate a block. (See pasted
output in attachement.)
The host is a quite usual Debian stable (jessie) on amd64 but with ZFS by
zfsonlinux as filesystem. The volume has no compression or dedup options set.
--
You are receiving this mail because:
You are on the CC list for the bug.
next reply other threads:[~2016-03-29 21:01 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-03-29 21:01 bugzilla at busybox.net [this message]
2016-03-29 21:23 ` [Buildroot] [Bug 8831] image generation fails on host ZFS due to "no free space" bugzilla at busybox.net
2016-10-24 21:56 ` bugzilla at busybox.net
2017-03-25 13:44 ` bugzilla at busybox.net
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-8831-163@https.bugs.busybox.net/ \
--to=bugzilla@busybox.net \
--cc=buildroot@busybox.net \
/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