Uploaded image for project: 'RHEL'
  1. RHEL
  2. RHEL-76070

blkid doesn't show information about erofs image created on ppc64le

Linking RHIVOS CVEs to...Migration: Automation ...SWIFT: POC ConversionSync from "Extern...XMLWordPrintable

    • Icon: Bug Bug
    • Resolution: Done-Errata
    • Icon: Critical Critical
    • rhel-10.0
    • rhel-10.0
    • util-linux
    • None
    • util-linux-2.40.2-10.el10
    • No
    • Critical
    • rhel-plumbers
    • ssg_core_services
    • 28
    • 1
    • False
    • False
    • Hide

      None

      Show
      None
    • None
    • None
    • Rejected Blocker
    • None

      What were you trying to do that didn't work?

      I tried to create an erofs image on ppc64le and then print information about it using blkid. No info was printed by blkid. file recognized the image and printed something (notice that the UUID printed by file doesn't completely match the one printed by mkfs.erofs):

      [root@ibm-p9z-23-lp12 ~]# mkdir test
      [root@ibm-p9z-23-lp12 ~]# mkfs.erofs test_ppc64le.img test
      mkfs.erofs 1.8.4
      Build completed.
      ------
      Filesystem UUID: f858b060-e775-412a-a45b-2aa9a694ec13
      Filesystem total blocks: 1 (of 65536-byte blocks)
      Filesystem total inodes: 1
      Filesystem total metadata blocks: 1
      Filesystem total deduplicated bytes (of source files): 0
      [root@ibm-p9z-23-lp12 ~]# blkid test_ppc64le.img 
      [root@ibm-p9z-23-lp12 ~]#
      [root@ibm-p9z-23-lp12 ~]# file test_ppc64le.img
      test_ppc64le.img: EROFS filesystem, compat: SB_CHKSUM MTIME, blocksize=16, exslots=0, uuid=60B058F8-75E7-2A41-A45B-2AA9A694EC13
      [root@ibm-p9z-23-lp12 ~]# 

       

      The same steps work fine on the other architectures (x86_64/aarch64/s390x), see the blkid output on x86_64 (although the UUID printed by file is still incorrect):

      [root@kvm-03-guest16 ~]# mkdir test
      [root@kvm-03-guest16 ~]# mkfs.erofs test_x86_64.img test
      mkfs.erofs 1.8.4
      Build completed.
      ------
      Filesystem UUID: 6445a18d-62a5-4a06-ad2a-dafddcce2886
      Filesystem total blocks: 1 (of 4096-byte blocks)
      Filesystem total inodes: 1
      Filesystem total metadata blocks: 1
      Filesystem total deduplicated bytes (of source files): 0
      [root@kvm-03-guest16 ~]#
      [root@kvm-03-guest16 ~]# blkid test_x86_64.img 
      test_x86_64.img: UUID="6445a18d-62a5-4a06-ad2a-dafddcce2886" BLOCK_SIZE="4096" TYPE="erofs"
      [root@kvm-03-guest16 ~]#
      [root@kvm-03-guest16 ~]# file test_x86_64.img
      test_x86_64.img: EROFS filesystem, compat: SB_CHKSUM MTIME, blocksize=12, exslots=0, uuid=8DA14564-A562-064A-AD2A-DAFDDCCE2886
      [root@kvm-03-guest16 ~]#
      

       

      It should be mentioned, that:

      • blkid running on x86_64 also doesn't print any info about test_ppc64le.img.
      • blkid running on ppc64le prints info about test_x86_64.img.
      • file running on x86_64 or ppc64le prints info about both images, although the reported UUIDs don't match the ones reported by mkfs.erofs when creating the images. That's probably a different issue, but mentioning this observation here as well.
         

      The problem was found while testing bug RHEL-48606, where the ppc64le installer built with the erofs rootfs failed to start:

      ...
      [   10.845649] env2: Budget exhausted after napi rescheduled
      env2: Budget exhausted after napi rescheduled
      100  562M  100  562M    0     0   112M      0  0:00:05  0:00:05 --:--:--  112M
      [   15.935501] dracut-initqueue[1346]: modprobe: FATAL: Module  not found in directory /lib/modules/6.12.0-43.el10.ppc64le
      [   15.948864] loop: module loaded
      [   15.949447] loop0: detected capacity change from 0 to 1151616
      loop: module loaded
      loop0: detected capacity change from 0 to 1151616
      [   15.958317] loop1: detected capacity change from 0 to 67108864
      loop1: detected capacity change from 0 to 67108864
      [  OK  ] Started cancel-multipath-wait-sda.…ting for multipath siblings of sda.
      [  OK  ] Finished dracut-initqueue.service - dracut initqueue hook.
      [  OK  ] Reached target remote-fs-pre.targe…reparation for Remote File Systems.
      [  OK  ] Reached target remote-cryptsetup.target - Remote Encrypted Volumes.
      [  OK  ] Reached target remote-fs.target - Remote File Systems.
               Starting dracut-pre-mount.service - dracut pre-mount hook...
      [  OK  ] Finished dracut-pre-mount.service - dracut pre-mount hook.
      [  OK  ] Reached target initrd-root-fs.target - Initrd Root File System.
               Starting initrd-parse-etc.service …ints Configured in the Real Root...
               Stopping multipathd.service - Devi…pper Multipath Device Controller...
      [  OK  ] Finished initrd-parse-etc.service …points Configured in the Real Root.
      [  OK  ] Reached target initrd-fs.target - Initrd File Systems.
      [  OK  ] Reached target initrd.target - Initrd Default Target.
               Starting dracut-mount.service - dracut mount hook...
      [   40.670998] dracut-mount[2032]: mount: /sysroot: fsconfig system call failed: Can't find a SQUASHFS superblock on dm-0.
      [   40.671057] dracut-mount[2032]:        dmesg(1) may have more information after failed mount system call.
      [   40.685368] dracut-mount[2046]: mount: /sysroot: fsconfig system call failed: Can't find a SQUASHFS superblock on dm-0.
      [   40.685444] dracut-mount[2046]:        dmesg(1) may have more information after failed mount system call.
      [   40.699634] dracut-mount[2060]: mount: /sysroot: fsconfig system call failed: Can't find a SQUASHFS superblock on dm-0.
      [   40.699710] dracut-mount[2060]:        dmesg(1) may have more information after failed mount system call.
      ...
      

       

      What is the impact of this issue to you?

      Broken installer on ppc64le. Unable to use erofs instead of squashfs for the installer image.

      Please provide the package NVR for which the bug is seen:

      erofs-utils-1.8.4-2.el10.ppc64le
      util-linux-core-2.40.2-5.el10.ppc64le
      file-5.45-7.el10

      How reproducible is this bug?:

      Every time for an erofs image built on ppc64le.

      Steps to reproduce on ppc64le:

      1. mkdir test
      2. mkfs.erofs test_ppc64le.img test
      3. blkid test_ppc64le.img

      Expected results

      blkid prints info about the image.

      Actual results

      No info is printed by blkid.

              rhn-engineering-kzak Karel Zak
              jstodola@redhat.com Jan Stodola
              Karel Zak Karel Zak
              Radka Brychtova Radka Brychtova
              Votes:
              0 Vote for this issue
              Watchers:
              9 Start watching this issue

                Created:
                Updated:
                Resolved: