From: Jan Kiszka <jan.kiszka@siemens.com>
To: benbrenson89@googlemail.com, isar-users <isar-users@googlegroups.com>
Subject: Re: Bug mcopy (wic) when creating bootpartition
Date: Thu, 27 Feb 2020 17:10:15 +0100 [thread overview]
Message-ID: <145aeb1f-5c47-d1e7-e772-e46ecb6512c2@siemens.com> (raw)
In-Reply-To: <f95d6dec-0ae6-45aa-8deb-fbc5df71beb6@googlegroups.com>
On 27.02.20 13:33, benbrenson89 via isar-users wrote:
> Hi Jan,
>
> Current architecture: armhf
> Qemu: qemu-arm-static
>
> To reproduce the bug I jumped into the buildchroot and typed the following:
>
>
> I tested it with mcopy version 4.0.18 and 4.0.23, with same results.
>
> sudo chroot buildchroot-target-debian-buster-armhf/rootfs
> cd /tmp
> mkdosfs -n test -S 512 -C test.img $((512*2*1024*100))
> mkdir testfolder
> touch testfolder/testtestfile1
> touch testfolder/testtestfile1
> export MTOOLS_SKIP_CHECK=1
> mcopy -v -i test.img -s testfolder/ ::/
> > Copying testfolder
If you chroot into that rootfs on an ARM target (I suppose QEMU would be
fine as well), does it then work? That would be the smoking gun for
qemu-user. If so, using qemu-user from testing might be worth a try.
Jan
--
Siemens AG, Corporate Technology, CT RDA IOT SES-DE
Corporate Competence Center Embedded Linux
next prev parent reply other threads:[~2020-02-27 16:10 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-02-27 9:32 benbrenson89
2020-02-27 9:42 ` Jan Kiszka
2020-02-27 12:33 ` benbrenson89
2020-02-27 16:10 ` Jan Kiszka [this message]
2020-03-09 17:04 ` Henning Schild
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=145aeb1f-5c47-d1e7-e772-e46ecb6512c2@siemens.com \
--to=jan.kiszka@siemens.com \
--cc=benbrenson89@googlemail.com \
--cc=isar-users@googlegroups.com \
/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