public inbox for isar-users@googlegroups.com
 help / color / mirror / Atom feed
From: Jan Kiszka <jan.kiszka@siemens.com>
To: isar-users <isar-users@googlegroups.com>
Subject: Strange zero block size, wic fails
Date: Mon, 3 Jul 2017 14:36:00 +0200	[thread overview]
Message-ID: <a26b3719-0de6-f99f-33eb-95a7b793fa4f@siemens.com> (raw)

Hi all,

any spontaneous idea what could cause such a bug?

INFO: Creating image(s)...

Traceback (most recent call last):
  File "/isar/scripts/wic", line 303, in <module>
    sys.exit(main(sys.argv[1:]))
  File "/isar/scripts/wic", line 298, in main
    return hlp.invoke_subcommand(args, parser, hlp.wic_help_usage, subcommands)
  File "/isar/scripts/lib/wic/help.py", line 97, in invoke_subcommand
    subcommands.get(args[0], subcommand_error)[0](args[1:], usage)
  File "/isar/scripts/wic", line 236, in wic_create_subcommand
    engine.wic_create(wks_file, rootfs_dir, bootimg_dir, kernel_dir, options)
  File "/isar/scripts/lib/wic/engine.py", line 191, in wic_create
    plugin.do_create()
  File "/isar/scripts/lib/wic/plugins/imager/direct.py", line 94, in do_create
    self.assemble()
  File "/isar/scripts/lib/wic/plugins/imager/direct.py", line 185, in assemble
    self._image.assemble()
  File "/isar/scripts/lib/wic/plugins/imager/direct.py", line 544, in assemble
    sparse_copy(source, self.path, part.start * self.sector_size)
  File "/isar/scripts/lib/wic/filemap.py", line 537, in sparse_copy
    fmap = api(src_fname)
  File "/isar/scripts/lib/wic/filemap.py", line 529, in filemap
    return FilemapFiemap(image, log)
  File "/isar/scripts/lib/wic/filemap.py", line 347, in __init__
    _FilemapBase.__init__(self, image, log)
  File "/isar/scripts/lib/wic/filemap.py", line 98, in __init__
    self.blocks_cnt //= self.block_size
ZeroDivisionError: integer division or modulo by zero


We confirmed via instrumentation that there is actually 0 returned by
get_block_size, more precisely when requesting the info for the
temporary boot.img.

Base system was a Debian 8.8 with latest Docker release, and the run
took place inside that container (kasproject/kas-isar:latest). I'm
currently trying to reproduce locally.

Jan

-- 
Siemens AG, Corporate Technology, CT RDA ITP SES-DE
Corporate Competence Center Embedded Linux

             reply	other threads:[~2017-07-03 12:36 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-07-03 12:36 Jan Kiszka [this message]
2017-07-05 12:05 ` Jan Kiszka

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=a26b3719-0de6-f99f-33eb-95a7b793fa4f@siemens.com \
    --to=jan.kiszka@siemens.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