appliance-tools

#15 appcreate: Ensure Btrfs volumes and subvolumes are set up first
Merged by ngompa. Opened by ngompa.
fix-mount-order-btrfs  into  master

This should ensure that the appliance image mount structure is
correct during image creation.

@dcavalca Please test this ASAP to verify this works so I can land this in Fedora before the next compose.

Getting

Losetup add /dev/loop0 mapping to /var/tmp/imgcreate-6kn4y6ca/tmp-h81pzpl5/Fedora-Xfce-armhfp-33-20200823.n.0-sda.raw
['btrfs.007', '/boot/efi', '/boot']
Formating btrfs filesystem on /dev/loop03
Formating args: ['mkfs.btrfs', '-L', '_btrfs.007', '/dev/loop03']
Creating mount point /var/tmp/imgcreate-6kn4y6ca/install_rootbtrfs.007
Mounting /dev/loop03 at /var/tmp/imgcreate-6kn4y6ca/install_rootbtrfs.007
ERROR: cannot create subvolume: Function not implemented
Create subvolume '/var/tmp/imgcreate-6kn4y6ca/install_rootbtrfs.007/root'
mount: /var/tmp/imgcreate-6kn4y6ca/install_root: mount(2) system call failed: No such file or directory.
ERROR: cannot create subvolume: Function not implemented
Create subvolume '/var/tmp/imgcreate-6kn4y6ca/install_rootbtrfs.007/home'
mount: /var/tmp/imgcreate-6kn4y6ca/install_root/home: mount(2) system call failed: No such file or directory.
Formating vfat filesystem on /dev/loop01
Formating args: ['mkfs.vfat', '/dev/loop01']
Creating mount point /var/tmp/imgcreate-6kn4y6ca/install_root/boot/efi
Mounting /dev/loop01 at /var/tmp/imgcreate-6kn4y6ca/install_root/boot/efi
Formating ext4 filesystem on /dev/loop02
Formating args: ['mkfs.ext4', '-F', '-L', '_/boot', '-m', '1', '-b', '4096', '/dev/loop02']
Tuning filesystem on /dev/loop02
Mounting /dev/loop02 at /var/tmp/imgcreate-6kn4y6ca/install_root/boot
mount: /var/tmp/imgcreate-6kn4y6ca/install_root/sys/fs/selinux/load: mount point does not exist.

using https://kojipkgs.fedoraproject.org//work/tasks/4670/49954670/koji-image-f33-build-49954670.ks and mock --root fedora-rawhide-armhfp --isolation=simple --chroot "/usr/bin/appliance-creator -c /koji-image-f33-build-49954670.ks d -v --logfile appliance.log --cache /tmp/koji-appliance -o app-output --format raw --name Fedora-Xfce-armhfp-33-20200823.n.0 --version 33 --release 20200823.n.0". And indeed it doesn't look like it was mounted properly:

[root@localhost ~]# cat /proc/mounts | grep /var/lib/mock
tmpfs /var/lib/mock/fedora-rawhide-armv7hl-bootstrap/root/proc tmpfs rw,seclabel,relatime 0 0
tmpfs /var/lib/mock/fedora-rawhide-armv7hl-bootstrap/root/sys tmpfs rw,seclabel,relatime 0 0
tmpfs /var/lib/mock/fedora-rawhide-armv7hl-bootstrap/root/dev/shm tmpfs rw,seclabel,relatime 0 0
devpts /var/lib/mock/fedora-rawhide-armv7hl-bootstrap/root/dev/pts devpts rw,seclabel,relatime,gid=5,mode=620,ptmxmode=666 0 0
/dev/sda3 /var/lib/mock/fedora-rawhide-armv7hl-bootstrap/root/var/cache/yum btrfs rw,seclabel,relatime,space_cache,subvolid=256,subvol=/root/var/cache/mock/fedora-rawhide-armv7hl-bootstrap/yum_cache 0 0
/dev/sda3 /var/lib/mock/fedora-rawhide-armv7hl-bootstrap/root/var/cache/dnf btrfs rw,seclabel,relatime,space_cache,subvolid=256,subvol=/root/var/cache/mock/fedora-rawhide-armv7hl-bootstrap/dnf_cache 0 0
tmpfs /var/lib/mock/fedora-rawhide-armv7hl/root/proc tmpfs rw,seclabel,relatime 0 0
tmpfs /var/lib/mock/fedora-rawhide-armv7hl/root/sys tmpfs rw,seclabel,relatime 0 0
tmpfs /var/lib/mock/fedora-rawhide-armv7hl/root/dev/shm tmpfs rw,seclabel,relatime 0 0
devpts /var/lib/mock/fedora-rawhide-armv7hl/root/dev/pts devpts rw,seclabel,relatime,gid=5,mode=620,ptmxmode=666 0 0
/dev/sda3 /var/lib/mock/fedora-rawhide-armv7hl/root/var/cache/yum btrfs rw,seclabel,relatime,space_cache,subvolid=256,subvol=/root/var/cache/mock/fedora-rawhide-armv7hl/yum_cache 0 0
/dev/sda3 /var/lib/mock/fedora-rawhide-armv7hl/root/var/cache/dnf btrfs rw,seclabel,relatime,space_cache,subvolid=256,subvol=/root/var/cache/mock/fedora-rawhide-armv7hl/dnf_cache 0 0
tmpfs /var/lib/mock/fedora-rawhide-armv7hl-bootstrap/root/var/lib/mock/fedora-rawhide-armv7hl/root tmpfs rw,seclabel,relatime 0 0
/dev/mapper/loop0p3 /var/lib/mock/fedora-rawhide-armv7hl/root/var/tmp/imgcreate-6kn4y6ca/install_rootbtrfs.007 btrfs rw,seclabel,relatime,ssd,space_cache,subvolid=5,subvol=/ 0 0
/dev/mapper/loop0p1 /var/lib/mock/fedora-rawhide-armv7hl/root/var/tmp/imgcreate-6kn4y6ca/install_root/boot/efi vfat rw,relatime,fmask=0002,dmask=0002,allow_utime=0020,codepage=437,iocharset=ascii,shortname=mixed,errors=remount-ro 0 0
/dev/mapper/loop0p2 /var/lib/mock/fedora-rawhide-armv7hl/root/var/tmp/imgcreate-6kn4y6ca/install_root/boot ext4 rw,seclabel,relatime 0 0
sysfs /var/lib/mock/fedora-rawhide-armv7hl/root/var/tmp/imgcreate-6kn4y6ca/install_root/sys sysfs rw,seclabel,nosuid,nodev,noexec,relatime 0 0
proc /var/lib/mock/fedora-rawhide-armv7hl/root/var/tmp/imgcreate-6kn4y6ca/install_root/proc proc rw,nosuid,nodev,noexec,relatime 0 0
devpts /var/lib/mock/fedora-rawhide-armv7hl/root/var/tmp/imgcreate-6kn4y6ca/install_root/dev/pts devpts rw,seclabel,relatime,gid=5,mode=620,ptmxmode=666 0 0
tmpfs /var/lib/mock/fedora-rawhide-armv7hl/root/var/tmp/imgcreate-6kn4y6ca/install_root/dev/shm tmpfs rw,seclabel,relatime 0 0
tmpfs /var/lib/mock/fedora-rawhide-armv7hl/root/var/tmp/imgcreate-6kn4y6ca/install_root/sys/fs/selinux tmpfs rw,seclabel,relatime 0 0
/dev/sda3 /var/lib/mock/fedora-rawhide-armv7hl/root/var/tmp/imgcreate-6kn4y6ca/install_root/var/cache/dnf btrfs rw,seclabel,relatime,space_cache,subvolid=256,subvol=/root/var/lib/mock/fedora-rawhide-armv7hl/root/tmp/koji-appliance 0 0
[root@localhost ~]#

unless I'm missing something.

With --debug: 

Adding disk sda as /var/tmp/imgcreate-8_yhm7op/tmp-kf4dbtw6/Fedora-Xfce-armhfp-33-20200823.n.0-sda.raw
Forcing disk label to msdos, because bootloader is extlinux-bootloader
Extending sparse file /var/tmp/imgcreate-8_yhm7op/tmp-kf4dbtw6/Fedora-Xfce-armhfp-33-20200823.n.0-sda.raw to 5863636992
Losetup add /dev/loop1 mapping to /var/tmp/imgcreate-8_yhm7op/tmp-kf4dbtw6/Fedora-Xfce-armhfp-33-20200823.n.0-sda.raw
Formatting disks
Initializing partition table for /dev/loop1 with msdos layout
Assigning partitions to disks
Assigned /boot/efi to sda1 at 4 at size 80
Assigned /boot to sda2 at 84 at size 512
Assigned btrfs.007 to sda3 at 596 at size 5000
Creating partitions
Add primary part at 4 of size 80
Part fstype: vfat, effective fstype fat32
Add primary part at 84 of size 512
Part fstype: ext4, effective fstype ext2
Add primary part at 596 of size 5000
Part fstype: btrfs, effective fstype btrfs
Dev loop1p1: /dev/loop11 -> /dev/mapper/loop1p1
Creating symlink from /dev/loop11 to /dev/mapper/loop1p1
Dev loop1p2: /dev/loop12 -> /dev/mapper/loop1p2
Creating symlink from /dev/loop12 to /dev/mapper/loop1p2
Dev loop1p3: /dev/loop13 -> /dev/mapper/loop1p3
Creating symlink from /dev/loop13 to /dev/mapper/loop1p3
Adding partx mapping for /dev/loop1
['btrfs.007', '/boot/efi', '/boot']
Formating btrfs filesystem on /dev/loop13
Formating args: ['mkfs.btrfs', '-L', '_btrfs.007', '/dev/loop13']
ERROR:
device
scan
failed
on
'/dev/loop13':
Function
not
implemented
btrfs-progs
v5.7
See
http://btrfs.wiki.kernel.org
for
more
information.
Detected
a
SSD,
turning
off
metadata
duplication.
Mkfs
with
-m
dup
if
you
want
to
force
metadata
duplication.
Label:
_btrfs.007
UUID:
b9ec4826-501e-4efa-9c26-d72c3e0fe160
Node
size:
16384
Sector
size:
4096
Filesystem
size:
4.66GiB
Block
group
profiles:
Data:
single
8.00MiB
Metadata:
single
8.00MiB
System:
single
4.00MiB
SSD
detected:
yes
Incompat
features:
extref,
skinny-metadata
Runtime
features:
Checksum:
crc32c
Number
of
devices:
1
Devices:
ID
SIZE
PATH
1
4.66GiB
/dev/loop13
Creating mount point /var/tmp/imgcreate-8_yhm7op/install_rootbtrfs.007
Mounting /dev/loop13 at /var/tmp/imgcreate-8_yhm7op/install_rootbtrfs.007
Creating Btrfs subvolume at path /var/tmp/imgcreate-8_yhm7op/install_rootbtrfs.007/root
ERROR: cannot create subvolume: Function not implemented
Create subvolume '/var/tmp/imgcreate-8_yhm7op/install_rootbtrfs.007/root'
Mounting Btrfs subvolume root at path /var/tmp/imgcreate-8_yhm7op/install_root/
mount: /var/tmp/imgcreate-8_yhm7op/install_root: mount(2) system call failed: No such file or directory.
Creating Btrfs subvolume at path /var/tmp/imgcreate-8_yhm7op/install_rootbtrfs.007/home
ERROR: cannot create subvolume: Function not implemented
Create subvolume '/var/tmp/imgcreate-8_yhm7op/install_rootbtrfs.007/home'
Mounting Btrfs subvolume home at path /var/tmp/imgcreate-8_yhm7op/install_root/home
mount: /var/tmp/imgcreate-8_yhm7op/install_root/home: mount(2) system call failed: No such file or directory.
Formating vfat filesystem on /dev/loop11
Formating args: ['mkfs.vfat', '/dev/loop11']
mkfs.fat
4.1
(2017-01-24)
Creating mount point /var/tmp/imgcreate-8_yhm7op/install_root/boot/efi
Mounting /dev/loop11 at /var/tmp/imgcreate-8_yhm7op/install_root/boot/efi
Setting boot flag on in /boot
Formating ext4 filesystem on /dev/loop12
Formating args: ['mkfs.ext4', '-F', '-L', '_/boot', '-m', '1', '-b', '4096', '/dev/loop12']
mke2fs
1.45.6
(20-Mar-2020)
Discarding
device
blocks:
4096/124928
done
Creating
filesystem
with
124928
4k
blocks
and
124928
inodes
Filesystem
UUID:
a78d80ca-f3dc-4ae2-913d-4c29d0980c16
Superblock
backups
stored
on
blocks:
32768,
98304
Allocating
group
tables:
0/4
done
Writing
inode
tables:
0/4
done
Creating
journal
(4096
blocks):
done
Writing
superblocks
and
filesystem
accounting
information:
0/4
done
Tuning filesystem on /dev/loop12
tune2fs
1.45.6
(20-Mar-2020)
Setting
maximal
mount
count
to
-1
Setting
interval
between
checks
to
0
seconds
Mounting /dev/loop12 at /var/tmp/imgcreate-8_yhm7op/install_root/boot
Writing mkinitrd config /var/tmp/imgcreate-8_yhm7op/install_root/etc/sysconfig/mkinitrd
mount: /var/tmp/imgcreate-8_yhm7op/install_root/sys/fs/selinux/load: mount point does not exist.

note the

Formating args: ['mkfs.btrfs', '-L', '_btrfs.007', '/dev/loop13']
ERROR:
device
scan
failed
on
'/dev/loop13':
Function
not
implemented

I'm not sure if this is a side effect of running in mock or not though.

It does look like a valid filesystem gets created and mounted on /var/lib/mock/fedora-rawhide-armv7hl/root/var/tmp/imgcreate-8_yhm7op/install_rootbtrfs.007 regardless of that error though, so it might be a red herring.

Converting the kickstart to run on x86_64 seems to indicate it works:

INFO: Running in chroot: ['/usr/bin/appliance-creator -c /koji-image-f33-build-49878217-x86_64.ks -d -v --logfile appliance.log --cache /tmp/koji-appliance -o app-output --format raw --name Fedora-Xfce-x86_64-Rawhide-20200822 --version Rawhide --release 20200822.n.0']
Start: chroot ['/usr/bin/appliance-creator -c /koji-image-f33-build-49878217-x86_64.ks -d -v --logfile appliance.log --cache /tmp/koji-appliance -o app-output --format raw --name Fedora-Xfce-x86_64-Rawhide-20200822 --version Rawhide --release 20200822.n.0']
No --ondisk specified in partition line of ks file; assuming 'sda'
No --ondisk specified in partition line of ks file; assuming 'sda'
No --ondisk specified in partition line of ks file; assuming 'sda'
Adding disk sda as /var/tmp/imgcreate-4uy_myy2/tmp-tlfhfodn/Fedora-Xfce-x86_64-Rawhide-20200822-sda.raw
Forcing disk label to msdos, because bootloader is extlinux-bootloader
Extending sparse file /var/tmp/imgcreate-4uy_myy2/tmp-tlfhfodn/Fedora-Xfce-x86_64-Rawhide-20200822-sda.raw to 5863636992
Losetup add /dev/loop0 mapping to /var/tmp/imgcreate-4uy_myy2/tmp-tlfhfodn/Fedora-Xfce-x86_64-Rawhide-20200822-sda.raw
Formatting disks
Initializing partition table for /dev/loop0 with msdos layout
Assigning partitions to disks
Assigned /boot/efi to sda1 at 4 at size 80
Assigned /boot to sda2 at 84 at size 512
Assigned btrfs.007 to sda3 at 596 at size 5000
Creating partitions
Add primary part at 4 of size 80
Part fstype: vfat, effective fstype fat32
Add primary part at 84 of size 512
Part fstype: ext4, effective fstype ext2
Add primary part at 596 of size 5000
Part fstype: btrfs, effective fstype btrfs
Dev loop0p1: /dev/loop01 -> /dev/mapper/loop0p1
Creating symlink from /dev/loop01 to /dev/mapper/loop0p1
Dev loop0p2: /dev/loop02 -> /dev/mapper/loop0p2
Creating symlink from /dev/loop02 to /dev/mapper/loop0p2
Dev loop0p3: /dev/loop03 -> /dev/mapper/loop0p3
Creating symlink from /dev/loop03 to /dev/mapper/loop0p3
Adding partx mapping for /dev/loop0
['btrfs.007', '/boot/efi', '/boot']
Formating btrfs filesystem on /dev/loop03
Formating args: ['mkfs.btrfs', '-L', '_btrfs.007', '/dev/loop03']
btrfs-progs
v5.7
See
http://btrfs.wiki.kernel.org
for
more
information.
Detected
a
SSD,
turning
off
metadata
duplication.
Mkfs
with
-m
dup
if
you
want
to
force
metadata
duplication.
Label:
_btrfs.007
UUID:
5edab5b1-da2b-4e88-8c4a-2c32de2c0a49
Node
size:
16384
Sector
size:
4096
Filesystem
size:
4.66GiB
Block
group
profiles:
Data:
single
8.00MiB
Metadata:
single
8.00MiB
System:
single
4.00MiB
SSD
detected:
yes
Incompat
features:
extref,
skinny-metadata
Runtime
features:
Checksum:
crc32c
Number
of
devices:
1
Devices:
ID
SIZE
PATH
1
4.66GiB
/dev/loop03
Creating mount point /var/tmp/imgcreate-4uy_myy2/install_rootbtrfs.007
Mounting /dev/loop03 at /var/tmp/imgcreate-4uy_myy2/install_rootbtrfs.007
Creating Btrfs subvolume at path /var/tmp/imgcreate-4uy_myy2/install_rootbtrfs.007/root
Create subvolume '/var/tmp/imgcreate-4uy_myy2/install_rootbtrfs.007/root'
Mounting Btrfs subvolume root at path /var/tmp/imgcreate-4uy_myy2/install_root/
Creating Btrfs subvolume at path /var/tmp/imgcreate-4uy_myy2/install_rootbtrfs.007/home
Create subvolume '/var/tmp/imgcreate-4uy_myy2/install_rootbtrfs.007/home'
Mounting Btrfs subvolume home at path /var/tmp/imgcreate-4uy_myy2/install_root/home
Formating vfat filesystem on /dev/loop01
Formating args: ['mkfs.vfat', '/dev/loop01']
mkfs.fat
4.1
(2017-01-24)
Creating mount point /var/tmp/imgcreate-4uy_myy2/install_root/boot/efi
Mounting /dev/loop01 at /var/tmp/imgcreate-4uy_myy2/install_root/boot/efi
Setting boot flag on in /boot
Formating ext4 filesystem on /dev/loop02
Formating args: ['mkfs.ext4', '-F', '-L', '_/boot', '-m', '1', '-b', '4096', '/dev/loop02']
mke2fs
1.45.6
(20-Mar-2020)
Discarding
device
blocks:
4096/124928
done
Creating
filesystem
with
124928
4k
blocks
and
124928
inodes
Filesystem
UUID:
185a0b4e-3fac-46a0-b045-81b474f306ed
Superblock
backups
stored
on
blocks:
32768,
98304
Allocating
group
tables:
0/4
done
Writing
inode
tables:
0/4
done
Creating
journal
(4096
blocks):
done
Writing
superblocks
and
filesystem
accounting
information:
0/4
done
Tuning filesystem on /dev/loop02
tune2fs
1.45.6
(20-Mar-2020)
Setting
maximal
mount
count
to
-1
Setting
interval
between
checks
to
0
seconds
Mounting /dev/loop02 at /var/tmp/imgcreate-4uy_myy2/install_root/boot
Writing mkinitrd config /var/tmp/imgcreate-4uy_myy2/install_root/etc/sysconfig/mkinitrd

Oh, except there's a problem... /boot/efi needs to be after /boot...

rebased onto 18fffb8e9784dd4d83bcdb94543e330e766a218a

@dcavalca Can you try again with this updated patch?

I'm still getting the same error when building for armhf, but I think it's unrelated to the change you made. How did you get it to work on x86_64?

@dcavalca I edited the kickstart to switch from armhfp to x86_64 and then used an x86_64 mock root instead of an armhfp one.

Looks like the partitions are in the right order now:

INFO: Running in chroot: ['/usr/bin/appliance-creator -c /koji-image-f33-build-49878217-x86_64.ks -d -v --logfile appliance.log --cache /tmp/koji-appliance -o app-output --format raw --name Fedora-Xfce-x86_64-Rawhide-20200822 --version Rawhide --release 20200822.n.0']
Start: chroot ['/usr/bin/appliance-creator -c /koji-image-f33-build-49878217-x86_64.ks -d -v --logfile appliance.log --cache /tmp/koji-appliance -o app-output --format raw --name Fedora-Xfce-x86_64-Rawhide-20200822 --version Rawhide --release 20200822.n.0']
No --ondisk specified in partition line of ks file; assuming 'sda'
No --ondisk specified in partition line of ks file; assuming 'sda'
No --ondisk specified in partition line of ks file; assuming 'sda'
Adding disk sda as /var/tmp/imgcreate-zc77mwdy/tmp-2zmtou4d/Fedora-Xfce-x86_64-Rawhide-20200822-sda.raw
Forcing disk label to msdos, because bootloader is extlinux-bootloader
Extending sparse file /var/tmp/imgcreate-zc77mwdy/tmp-2zmtou4d/Fedora-Xfce-x86_64-Rawhide-20200822-sda.raw to 5863636992
Losetup add /dev/loop1 mapping to /var/tmp/imgcreate-zc77mwdy/tmp-2zmtou4d/Fedora-Xfce-x86_64-Rawhide-20200822-sda.raw
Formatting disks
Initializing partition table for /dev/loop1 with msdos layout
Assigning partitions to disks
Assigned /boot/efi to sda1 at 4 at size 80
Assigned /boot to sda2 at 84 at size 512
Assigned btrfs.007 to sda3 at 596 at size 5000
Creating partitions
Add primary part at 4 of size 80
Part fstype: vfat, effective fstype fat32
Add primary part at 84 of size 512
Part fstype: ext4, effective fstype ext2
Add primary part at 596 of size 5000
Part fstype: btrfs, effective fstype btrfs
Dev loop1p1: /dev/loop11 -> /dev/mapper/loop1p1
Creating symlink from /dev/loop11 to /dev/mapper/loop1p1
Dev loop1p2: /dev/loop12 -> /dev/mapper/loop1p2
Creating symlink from /dev/loop12 to /dev/mapper/loop1p2
Dev loop1p3: /dev/loop13 -> /dev/mapper/loop1p3
Creating symlink from /dev/loop13 to /dev/mapper/loop1p3
Adding partx mapping for /dev/loop1
['btrfs.007', '/boot', '/boot/efi']
Formating btrfs filesystem on /dev/loop13
Formating args: ['mkfs.btrfs', '-L', '_btrfs.007', '/dev/loop13']
btrfs-progs
v5.7
See
http://btrfs.wiki.kernel.org
for
more
information.
Detected
a
SSD,
turning
off
metadata
duplication.
Mkfs
with
-m
dup
if
you
want
to
force
metadata
duplication.
Label:
_btrfs.007
UUID:
8a734d48-7e27-43f2-8e35-a3308eba1e7b
Node
size:
16384
Sector
size:
4096
Filesystem
size:
4.66GiB
Block
group
profiles:
Data:
single
8.00MiB
Metadata:
single
8.00MiB
System:
single
4.00MiB
SSD
detected:
yes
Incompat
features:
extref,
skinny-metadata
Runtime
features:
Checksum:
crc32c
Number
of
devices:
1
Devices:
ID
SIZE
PATH
1
4.66GiB
/dev/loop13
Creating mount point /var/tmp/imgcreate-zc77mwdy/install_rootbtrfs.007
Mounting /dev/loop13 at /var/tmp/imgcreate-zc77mwdy/install_rootbtrfs.007
Creating Btrfs subvolume at path /var/tmp/imgcreate-zc77mwdy/install_rootbtrfs.007/root
Create subvolume '/var/tmp/imgcreate-zc77mwdy/install_rootbtrfs.007/root'
Mounting Btrfs subvolume root at path /var/tmp/imgcreate-zc77mwdy/install_root/
Creating Btrfs subvolume at path /var/tmp/imgcreate-zc77mwdy/install_rootbtrfs.007/home
Create subvolume '/var/tmp/imgcreate-zc77mwdy/install_rootbtrfs.007/home'
Mounting Btrfs subvolume home at path /var/tmp/imgcreate-zc77mwdy/install_root/home
Setting boot flag on in /boot
Formating ext4 filesystem on /dev/loop12
Formating args: ['mkfs.ext4', '-F', '-L', '_/boot', '-m', '1', '-b', '4096', '/dev/loop12']
mke2fs
1.45.6
(20-Mar-2020)
Discarding
device
blocks:
4096/124928
done
Creating
filesystem
with
124928
4k
blocks
and
124928
inodes
Filesystem
UUID:
35029c5e-baf8-452c-95ba-608e69569b4a
Superblock
backups
stored
on
blocks:
32768,
98304
Allocating
group
tables:
0/4
done
Writing
inode
tables:
0/4
done
Creating
journal
(4096
blocks):
done
Writing
superblocks
and
filesystem
accounting
information:
0/4
done
Tuning filesystem on /dev/loop12
tune2fs
1.45.6
(20-Mar-2020)
Setting
maximal
mount
count
to
-1
Setting
interval
between
checks
to
0
seconds
Creating mount point /var/tmp/imgcreate-zc77mwdy/install_root/boot
Mounting /dev/loop12 at /var/tmp/imgcreate-zc77mwdy/install_root/boot
Formating vfat filesystem on /dev/loop11
Formating args: ['mkfs.vfat', '/dev/loop11']
mkfs.fat
4.1
(2017-01-24)
Creating mount point /var/tmp/imgcreate-zc77mwdy/install_root/boot/efi
Mounting /dev/loop11 at /var/tmp/imgcreate-zc77mwdy/install_root/boot/efi

Thanks. Yeah that looks much better indeed.

Pull-Request has been merged by ngompa

Cut https://pagure.io/fedora-btrfs/project/issue/11 to track the qemu/subvolume/loop device issue
Metadata
None
No Tags
Changes Summary 2
+0 -3
file changed
appcreate/appliance.py
+13 -2
file changed
appcreate/partitionedfs.py
Powered by Pagure 1.0.0
Documentation • File an Issue • About • SSH Hostkey/Fingerprint
© Red Hat, Inc. and others.