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

Error when specifying --config allocation/vdo_minimum_io_size=8 with vdo lvcreate command

    • Icon: Bug Bug
    • Resolution: Not a Bug
    • Icon: Major Major
    • None
    • rhel-10.0
    • lvm2 / VDO
    • None
    • No
    • Moderate
    • rhel-sst-logical-storage
    • ssg_filesystems_storage_and_HA
    • 2
    • False
    • Hide

      None

      Show
      None
    • None
    • None
    • None
    • Automated
    • x86_64
    • None

      This is similar to bugs https://issues.redhat.com/browse/RHEL-66612 and https://issues.redhat.com/browse/RHEL-67140 however when using "8", this happens in reverse. It's the "--config allocation/vdo_minimum_io_size" that fails.

      kernel-6.11.0-26.el10    BUILT: Fri Oct 25 07:28:01 AM CEST 2024
      lvm2-2.03.28-3.el10    BUILT: Thu Nov 14 10:40:47 AM CET 2024
      lvm2-libs-2.03.28-3.el10    BUILT: Thu Nov 14 10:40:47 AM CET 2024
      
      
      # Only one works
      [root@virt-485 ~]# lvcreate --yes --type vdo --config allocation/vdo_minimum_io_size=8 -L 10G vdo_sanity -V100G
        VDO minimum io size 0 is unsupported [512, 4096].
        Run `lvcreate --help' for more information.
      [root@virt-485 ~]# lvcreate --yes --type vdo --vdosettings minimum_io_size=8 -L 10G vdo_sanity -V100G
        Wiping vdo signature on /dev/vdo_sanity/vpool4.
          The VDO volume can address 6.00 GB in 3 data slabs, each 2.00 GB.
          It can grow to address at most 16.00 TB of physical storage in 8192 slabs.
          If a larger maximum size might be needed, use bigger slabs.
        Logical volume "lvol4" created.
      
      
      # Both now work 
      [root@virt-485 ~]# lvcreate --yes --type vdo --config allocation/vdo_minimum_io_size=512 -L 10G vdo_sanity -V100G  
        Wiping vdo signature on /dev/vdo_sanity/vpool0.
          The VDO volume can address 6.00 GB in 3 data slabs, each 2.00 GB.
          It can grow to address at most 16.00 TB of physical storage in 8192 slabs.
          If a larger maximum size might be needed, use bigger slabs.
        Logical volume "lvol0" created.
      [root@virt-485 ~]# lvcreate --yes --type vdo --vdosettings minimum_io_size=512 -L 10G vdo_sanity -V100G
        Wiping vdo signature on /dev/vdo_sanity/vpool1.
          The VDO volume can address 6.00 GB in 3 data slabs, each 2.00 GB.
          It can grow to address at most 16.00 TB of physical storage in 8192 slabs.
          If a larger maximum size might be needed, use bigger slabs.
        Logical volume "lvol1" created.
       
       
      # Both now work 
      [root@virt-485 ~]# lvcreate --yes --type vdo --config allocation/vdo_minimum_io_size=4096 -L 10G vdo_sanity -V100G
        Wiping vdo signature on /dev/vdo_sanity/vpool2.
          The VDO volume can address 6.00 GB in 3 data slabs, each 2.00 GB.
          It can grow to address at most 16.00 TB of physical storage in 8192 slabs.
          If a larger maximum size might be needed, use bigger slabs.
        Logical volume "lvol2" created.
      [root@virt-485 ~]# lvcreate --yes --type vdo --vdosettings minimum_io_size=4096 -L 10G vdo_sanity -V100G
        Wiping vdo signature on /dev/vdo_sanity/vpool3.
          The VDO volume can address 6.00 GB in 3 data slabs, each 2.00 GB.
          It can grow to address at most 16.00 TB of physical storage in 8192 slabs.
          If a larger maximum size might be needed, use bigger slabs.
        Logical volume "lvol3" created.
      

              zkabelac@redhat.com Zdenek Kabelac
              cmarthal@redhat.com Corey Marthaler
              lvm-team lvm-team
              Cluster QE Cluster QE
              Votes:
              0 Vote for this issue
              Watchers:
              7 Start watching this issue

                Created:
                Updated:
                Resolved: