Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]

Groups > linux.debian.bugs.dist > #1181872

Bug#1060416: mmdebstrap-autopkgtest-build-qemu fails on mkfs.ext4; does it require a 25 GiB TMPDIR?

Show all headers | View raw

Package: mmdebstrap
Version: 1.4.0-1
Severity: normal

Hello,
I am giving mmdebstrap-autopkgtest-build-qemu a try.

The following command fails:

  $ mmdebstrap-autopkgtest-build-qemu --boot=efi sid sid_amd64.img

during some package installation with "no space left on device" error,
since I have /tmp on a somewhat small physical partition:

  $ df --si /tmp/
  Filesystem      Size  Used Avail Use% Mounted on
  /dev/md3        868M   99k  806M   1% /tmp

I tried with a TMPDIR in system memory:

  $ TMPDIR=/dev/shm mmdebstrap-autopkgtest-build-qemu \
                    --boot=efi sid sid_amd64.img

but it again fails with the following (final chunk of) output:

  [...]
  cp: warning: behavior of -n is non-portable and may change in future; use --update=none instead
  I: running special hook: download vmlinuz '/dev/shm/tmp.uNRUbVgiOu/kernel'
  I: running special hook: download initrd.img '/dev/shm/tmp.uNRUbVgiOu/initrd'
  I: running --customize-hook in shell: sh -c 'mount --bind "$1" "$1/mnt"' exec /dev/shm/mmdebstrap.IXehDNUWIf
  I: running --customize-hook in shell: sh -c 'mount --bind "$1/mnt/mnt" "$1/mnt/dev"' exec /dev/shm/mmdebstrap.IXehDNUWIf
  I: running --customize-hook in shell: sh -c '/sbin/mkfs.ext4 -d "$1/mnt" -L autopkgtestvm -E 'offset=134217728,assume_storage_prezeroed=1' 'sid_amd64.img' '25G'' exec /dev/shm/mmdebstrap.IXehDNUWIf
  mke2fs 1.47.0 (5-Feb-2023)
  mkfs.ext4: Permission denied while trying to determine filesystem size
  E: setup failed: E: command failed: /sbin/mkfs.ext4 -d "$1/mnt" -L autopkgtestvm -E 'offset=134217728,assume_storage_prezeroed=1' 'sid_amd64.img' '25G'
  W: hooklistener errored out: E: received eof on socket
  
  I: main() received signal PIPE: waiting for setup...
  I: removing tempdir /dev/shm/mmdebstrap.IXehDNUWIf...
  E: mmdebstrap failed to run
  mmdebstrap failed

Does it fail because I do not have enough system memory?

  $ df --si /dev/shm/
  Filesystem      Size  Used Avail Use% Mounted on
  tmpfs           8.3G  108M  8.2G   2% /dev/shm

Is this the explanation?
Otherwise, what went wrong?

By the way, the old script that used guestfish (with all its limitations)
was able to create a QEMU image in .qcow2 format and my /dev/shm was
enough for it to work correctly.
Why does the current mmdebstrap-autopkgtest-build-qemu create a QEMU
image in .img format? Isn't the .qcow2 format better?

Please clarify and/or improve mmdebstrap-autopkgtest-build-qemu .
Thanks for your time!


-- System Information:
Debian Release: trixie/sid
  APT prefers testing
  APT policy: (800, 'testing'), (500, 'unstable')
Architecture: amd64 (x86_64)

Kernel: Linux 6.5.0-5-amd64 (SMP w/4 CPU threads; PREEMPT)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE=en_US:en
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

Versions of packages mmdebstrap depends on:
ii  apt      2.7.6
ii  perl     5.36.0-10+b1
ii  python3  3.11.4-5+b1

Versions of packages mmdebstrap recommends:
ii  arch-test            0.21-1
ii  fakechroot           2.20.1+ds-15
ii  fakeroot             1.32.2-1+b1
ii  gpg                  2.2.40-1.1+b1
ii  libdistro-info-perl  1.7
ii  libdpkg-perl         1.22.2
ii  mount                2.39.3-2
ii  uidmap               1:4.13+dfsg1-3+b1

Versions of packages mmdebstrap suggests:
pn  apt-transport-tor  <none>
ii  apt-utils          2.7.6
ii  ca-certificates    20230311
ii  debootstrap        1.0.134
ii  distro-info-data   0.60
ii  dpkg-dev           1.22.2
pn  genext2fs          <none>
ii  perl-doc           5.36.0-10
pn  qemu-user          <none>
pn  qemu-user-static   <none>
pn  squashfs-tools-ng  <none>
ii  systemd            255.2-3

-- no debconf information

Back to linux.debian.bugs.dist | Previous | Next — Next in thread | Find similar | Unroll thread

Thread

Bug#1060416: mmdebstrap-autopkgtest-build-qemu fails on mkfs.ext4; does it require a 25 GiB TMPDIR? "Francesco Poli (wintermute)" <invernomuto@paranoici.org> - 2024-01-11 00:00 +0100
  Bug#1060416: mmdebstrap-autopkgtest-build-qemu fails on mkfs.ext4; does it require a 25 GiB TMPDIR? Johannes Schauer Marin Rodrigues <josch@debian.org> - 2024-01-11 00:50 +0100
    Bug#1060416: mmdebstrap-autopkgtest-build-qemu fails on mkfs.ext4; does it require a 25 GiB TMPDIR? Francesco Poli <invernomuto@paranoici.org> - 2024-01-11 09:20 +0100
      Bug#1060416: mmdebstrap-autopkgtest-build-qemu fails on mkfs.ext4; does it require a 25 GiB TMPDIR? Johannes Schauer Marin Rodrigues <josch@debian.org> - 2024-01-11 21:10 +0100
        Bug#1060416: mmdebstrap-autopkgtest-build-qemu fails on mkfs.ext4; does it require a 25 GiB TMPDIR? Francesco Poli <invernomuto@paranoici.org> - 2024-01-12 20:10 +0100
          Bug#1060416: mmdebstrap-autopkgtest-build-qemu fails on mkfs.ext4; does it require a 25 GiB TMPDIR? Johannes Schauer Marin Rodrigues <josch@debian.org> - 2024-01-12 23:50 +0100
            Bug#1060416: mmdebstrap-autopkgtest-build-qemu fails on mkfs.ext4; does it require a 25 GiB TMPDIR? Francesco Poli <invernomuto@paranoici.org> - 2024-01-14 18:40 +0100
              Bug#1060416: mmdebstrap-autopkgtest-build-qemu fails on mkfs.ext4; does it require a 25 GiB TMPDIR? Johannes Schauer Marin Rodrigues <josch@debian.org> - 2024-01-15 17:50 +0100
          Bug#1060416: mmdebstrap-autopkgtest-build-qemu fails on mkfs.ext4; does it require a 25 GiB TMPDIR? Helmut Grohne <helmut@subdivi.de> - 2024-01-13 08:30 +0100
            Bug#1060416: mmdebstrap-autopkgtest-build-qemu fails on mkfs.ext4; does it require a 25 GiB TMPDIR? Johannes Schauer Marin Rodrigues <josch@debian.org> - 2024-01-13 20:30 +0100
              Bug#1060416: mmdebstrap-autopkgtest-build-qemu fails on mkfs.ext4; does it require a 25 GiB TMPDIR? Johannes Schauer Marin Rodrigues <josch@debian.org> - 2024-01-13 22:20 +0100
                Bug#1060416: mmdebstrap-autopkgtest-build-qemu fails on mkfs.ext4; does it require a 25 GiB TMPDIR? Francesco Poli <invernomuto@paranoici.org> - 2024-01-14 18:40 +0100
                Bug#1060416: mmdebstrap-autopkgtest-build-qemu fails on mkfs.ext4; does it require a 25 GiB TMPDIR? Helmut Grohne <helmut@subdivi.de> - 2024-01-15 07:40 +0100
                Bug#1060416: mmdebstrap-autopkgtest-build-qemu fails on mkfs.ext4; does it require a 25 GiB TMPDIR? Francesco Poli <invernomuto@paranoici.org> - 2024-01-16 00:30 +0100
                Bug#1060416: mmdebstrap-autopkgtest-build-qemu fails on mkfs.ext4; does it require a 25 GiB TMPDIR? Helmut Grohne <helmut@subdivi.de> - 2024-01-16 07:40 +0100
                Bug#1060416: mmdebstrap-autopkgtest-build-qemu fails on mkfs.ext4; does it require a 25 GiB TMPDIR? Johannes Schauer Marin Rodrigues <josch@debian.org> - 2024-01-16 11:10 +0100
                Bug#1060416: mmdebstrap-autopkgtest-build-qemu fails on mkfs.ext4; does it require a 25 GiB TMPDIR? Johannes Schauer Marin Rodrigues <josch@debian.org> - 2024-01-23 09:10 +0100
                Bug#1060416: mmdebstrap-autopkgtest-build-qemu fails on mkfs.ext4; does it require a 25 GiB TMPDIR? Johannes Schauer Marin Rodrigues <josch@debian.org> - 2024-01-25 13:40 +0100
                Bug#1060416: mmdebstrap-autopkgtest-build-qemu fails on mkfs.ext4; does it require a 25 GiB TMPDIR? Francesco Poli <invernomuto@paranoici.org> - 2024-01-27 19:00 +0100

csiph-web