All of lore.kernel.org
 help / color / mirror / Atom feed
From: bugzilla@busybox.net
To: buildroot@uclibc.org
Subject: [Buildroot] [Bug 14196] when using raspberrypicm4io_64_defconfig, make fails with mkfs.ext4: No such file or directory while trying to determine filesystem size
Date: Sun, 05 Sep 2021 16:46:10 +0000	[thread overview]
Message-ID: <bug-14196-163-oY7xtsnzCJ@https.bugs.busybox.net/> (raw)
In-Reply-To: <bug-14196-163@https.bugs.busybox.net/>

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

--- Comment #1 from Yann E. MORIN <yann.morin.1998@free.fr> ---
Leon, All,

Thanks the report. I can confirm indeed that e2fsprogs 1.46.3 now requirtes
that
the file where to generate the filesystem must pre-exist. This is a regression
in
2fsprogs itself.; indeed, I've tested 1.46.2 and 1.46.4, and both work without
the touch.

And indeed, the e2fsprogs commit53464654bd33 (mke2fs: fix creating a file
system
image w/o a pre-existing file) states:

    By deferring the call to check_plausible() in commit
    942b00cb9d2f ("mke2fs: do not warn about a pre-existing partition
    table when using a non-zero offset") this behaviour was broken.

I'll try to see if we can cook up a backport of that commit for the 2021.08.x
branch. For master, a bump to 1.46.4 will fix the issue.

Regards,
Yann E. MORIN.

-- 
You are receiving this mail because:
You are on the CC list for the bug.
_______________________________________________
buildroot mailing list
buildroot@lists.buildroot.org
https://lists.buildroot.org/mailman/listinfo/buildroot

  parent reply	other threads:[~2021-09-05 16:46 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-09-05 11:16 [Buildroot] [Bug 14196] New: when using raspberrypicm4io_64_defconfig, make fails with mkfs.ext4: No such file or directory while trying to determine filesystem size bugzilla
2021-09-05 14:39 ` [Buildroot] [Bug 14196] " bugzilla
2021-09-05 16:46 ` bugzilla [this message]
2021-09-05 18:42 ` bugzilla
2021-09-11 10:04 ` bugzilla

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-14196-163-oY7xtsnzCJ@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.