~sircmpwn/sr.ht-discuss

2 2

archlinux genimg script issues with qemu-nbd?

Details
Message ID
<20200123050348.GA140275@michaels.world>
DKIM signature
missing
Download raw message
I'm trying to generate an archlinux builds image on archlinux, and it gets to the point where it's initializing the filesystem, and hangs. I get the following output before the hang:

[root@archlinux archlinux]# ./genimg
+ root=root
+ arch=x86_64
+ mkdir -p x86_64
+ qemu-img create -f qcow2 x86_64/root.img.qcow2 20G
Formatting 'x86_64/root.img.qcow2', fmt=qcow2 size=21474836480 cluster_size=65536 lazy_refcounts=off refcount_bits=16
+ modprobe nbd
+ qemu-nbd --connect=/dev/nbd0 x86_64/root.img.qcow2
+ trap cleanup EXIT
+ mkdir -p root
+ mkfs.ext4 /dev/nbd0
mke2fs 1.45.5 (07-Jan-2020)
Discarding device blocks: failed - Input/output error
Creating filesystem with 5242880 4k blocks and 1310720 inodes
Filesystem UUID: cb02a523-e846-4b2b-a820-a94569bb60db
Superblock backups stored on blocks:
         32768, 98304, 163840, 229376, 294912, 819200, 884736, 1605632, 2654208,
         4096000

Allocating group tables: done
Writing inode tables: done
Creating journal (32768 blocks):

Also of note, in the dmesg I get a message like the following:

block nbd0: Other side returned error (5)

Any idea what could be causing this? I know the qemu-nbd process of making a disk image worked in the past, but for whatever reason now it's hanging.
-Michael.
Details
Message ID
<C039VMOMOC2C.368KXJYA1235C@homura>
In-Reply-To
<20200123050348.GA140275@michaels.world> (view parent)
DKIM signature
missing
Download raw message
Hm, I've never run into this. Have you tried it on a fresh Arch install?
Our daily Arch Linux rebuilds have been running this script without
issues for some time:

https://builds.sr.ht/~sircmpwn/archlinux
Details
Message ID
<20200126005224.GA411609@michaels.world>
In-Reply-To
<C039VMOMOC2C.368KXJYA1235C@homura> (view parent)
DKIM signature
missing
Download raw message
I just rebuild a fresh arch machine to test this. FWIW, it's running on a vm (both), but it also did work maybe a month ago. The new vm also had the same problem. Just in case that gives any ideas -- I think it must be a vm specific issue that recently cropped up, probably something the host is missing.
-Michael.




On Thu, Jan 23, 2020 at 10:23:14AM -0500, Drew DeVault wrote:
>Hm, I've never run into this. Have you tried it on a fresh Arch install?
>Our daily Arch Linux rebuilds have been running this script without
>issues for some time:
>
>https://builds.sr.ht/~sircmpwn/archlinux