[Buildroot] [Bug 8831] New: image generation fails on host ZFS due to "no free space"

[Buildroot] [Bug 8831] New: image generation fails on host ZFS due to "no free space"

[bugzilla at busybox.net]

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.

[Buildroot] [Bug 8831] image generation fails on host ZFS due to "no free space"

[bugzilla at busybox.net]

https://bugs.busybox.net/show_bug.cgi?id=8831

Yann E. MORIN <yann.morin.1998@free.fr> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|NEW                         |ASSIGNED
           Assignee|unassigned at buildroot.uclibc |yann.morin.1998 at free.fr
                   |.org                        |
                 CC|                            |yann.morin.1998 at free.fr

--- Comment #1 from Yann E. MORIN <yann.morin.1998@free.fr> ---
Maybe it's time we switch to use e2fsprogs from their 'next' branch,
rather than our canned script?

The upstream e2fsprogs now has the ability to fill-in the generated
filesystem from the content of an existing directory (with the new -d
option).

FWIW, Debian is now using a snapshot of 2016-03-15 in Stretch (testing)
and they have a single patch on top of that. I'd rather trust Debian.

Regards,
Yann E. MORIN.

-- 
You are receiving this mail because:
You are on the CC list for the bug.

[Buildroot] [Bug 8831] image generation fails on host ZFS due to "no free space"

[bugzilla at busybox.net]

https://bugs.busybox.net/show_bug.cgi?id=8831

--- Comment #2 from Thomas Petazzoni <thomas.petazzoni@free-electrons.com> ---
FWIW, the current release of e2fsprogs we have in Buildroot can generate
filesystem images:

./output/host/usr/sbin/mke2fs -d fs/ test.img 1024

However, it will *not* solve the problem: you still have to pass the size of
the filesystem to be created, either in number of blocks or in KB/MB/GB.
Therefore, we still have to estimate it (like we're doing today), and
potentially get it wrong.

Maybe it is simply impossible to automatically calculate the filesystem size,
and we should stop supporting auto-calculation, and instead ask the user to
fill in a size for the filesystem (either in blocks or KB/MB/GB).

Thoughts?

-- 
You are receiving this mail because:
You are on the CC list for the bug.

[Buildroot] [Bug 8831] image generation fails on host ZFS due to "no free space"

[bugzilla at busybox.net]

https://bugs.busybox.net/show_bug.cgi?id=8831

Thomas Petazzoni <thomas.petazzoni@free-electrons.com> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|ASSIGNED                    |RESOLVED
         Resolution|---                         |FIXED

--- Comment #3 from Thomas Petazzoni <thomas.petazzoni@free-electrons.com> ---
We have dropped support for auto-calculating the size of the ext2 filesystem:
the size *must* now be passed in a Buildroot option. See
https://git.buildroot.org/buildroot/commit/?id=c6bca8cef0310bc649240b451989457ce94a8358.

Therefore, the issue raised by this bug can no longer be encountered.

-- 
You are receiving this mail because:
You are on the CC list for the bug.