Fails to produce a loop-mountable FS on powerpc/armhf
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
cloud-images |
Fix Released
|
High
|
Dan Watkins | ||
e2fsprogs (Ubuntu) |
Invalid
|
Undecided
|
Unassigned |
Bug Description
In yakkety cloud image builds for each of powerpc and armhf (but not amd64, i386, ppc64el, arm64 or s390x) we see the following failure:
[2016-07-01 09:51:08] lb_binary_chroot
P: Begin copying chroot...
[2016-07-01 09:51:08] lb_binary_rootfs
P: Begin building root filesystem image...
0+0 records in
0+0 records out
0 bytes copied, 3.7116e-05 s, 0.0 kB/s
mke2fs 1.43.1 (08-Jun-2016)
ext2fs_
Suggestion: Use Linux kernel >= 3.18 for improved stability of the metadata and journal checksum features.
Discarding device blocks: 4096/343040
Creating filesystem with 343040 4k blocks and 171600 inodes
Filesystem UUID: 43ff7fc9-
Superblock backups stored on blocks:
32768, 98304, 163840, 229376, 294912
Allocating group tables: 0/11 done
Writing inode tables: 0/11 done
Creating journal (8192 blocks): done
Writing superblocks and filesystem accounting information: 0/11 done
mount: wrong fs type, bad option, bad superblock on /dev/loop0,
missing codepage or helper program, or other error
In some cases useful info is found in syslog - try
dmesg | tail or so.
This is caused by this code in live-build's lb_binary_rootfs script:
dd if=/dev/zero of=binary/
mkfs.${
mkdir -p filesystem.tmp
${LB_ROOT_COMMAND} mount -o loop binary/
Changed in cloud-images: | |
status: | New → In Progress |
Changed in cloud-images: | |
milestone: | y-2016-07-28 → y-2016-08-11 |
Changed in cloud-images: | |
milestone: | y-2016-08-11 → y-2016-08-25 |
e2fsprogs was sync'd to 1.43.1-1 from Debian (where previously Ubuntu had 1.42.13-1ubuntu1) in the time between our last successful build and the first failure.