大网数据广告活动
服务器运维问答

Struggling to grow my physical VDO size after MD grow

· 52CE 我爱测

I'm hitting a bit of a brick wall here with vdo growPhysical -n pool . I've recently replaced my 3TB HDD's with 4TB HDD's in an md RAID5 array, which is now showing the correct capacity (8TB) but not allowing expansion of the VDO…

问题原文

原帖链接 · mcmeeking · CC BY-SA 4.0

I'm hitting a bit of a brick wall here with vdo growPhysical -n pool. I've recently replaced my 3TB HDD's with 4TB HDD's in an md RAID5 array, which is now showing the correct capacity (8TB) but not allowing expansion of the VDO backing.

sudo mdadm --detail /dev/md/md0 output:

# mdadm --detail /dev/md/md0
/dev/md/md0:
           Version : 1.2
     Creation Time : Wed Mar 18 20:26:50 2020
        Raid Level : raid5
        Array Size : 7813772288 (7451.79 GiB 8001.30 GB)
     Used Dev Size : 3906886144 (3725.90 GiB 4000.65 GB)
      Raid Devices : 3
     Total Devices : 3
       Persistence : Superblock is persistent

     Intent Bitmap : Internal

       Update Time : Wed Jun 10 22:01:31 2020
             State : clean 
    Active Devices : 3
   Working Devices : 3
    Failed Devices : 0
     Spare Devices : 0

            Layout : left-symmetric
        Chunk Size : 512K

Consistency Policy : bitmap

              Name : ocelot:md0  (local to host ocelot)
              UUID : 17c8828b:5b1d7435:063a40ff:18285a8e
            Events : 42696

    Number   Major   Minor   RaidDevice State
       4       8       16        0      active sync   /dev/sdb
       5       8       32        1      active sync   /dev/sdc
       3       8       48        2      active sync   /dev/sdd

sudo vdo growPhysical -n pool --verbose output:

    vdodumpconfig /dev/disk/by-id/md-uuid-17c8828b:5b1d7435:063a40ff:18285a8e
    dmsetup status --target vdo pool
    dmsetup resume pool
    vdodmeventd -r pool
    dmsetup status --target vdo pool
    readlink -f /dev/disk/by-id/md-uuid-17c8828b:5b1d7435:063a40ff:18285a8e
    cat /sys/class/block/md0/size
    dmsetup table pool
    dmsetup reload pool --table '0 35161595904 vdo V2 /dev/disk/by-id/md-uuid-17c8828b:5b1d7435:063a40ff:18285a8e 1953443072 4096 32768 16380 on auto pool maxDiscard 1 ack 1 bio 4 bioRotationInterval 64 cpu 2 hash 1 logical 1 physical 1'
vdo: ERROR - Device pool could not be changed; device-mapper: reload ioctl on pool  failed: Input/output error
vdo: ERROR - device-mapper: reload ioctl on pool  failed: Input/output error

Just looking for an indication where I'm going wrong here if anything, I've tried through CLI and cockpit and neither have yielded the change I'm looking for. Is this change just not implemented yet?

I've also tried deactivating the VDO device and then attempting to grow while it's offline but when I do that I just get:

    dmsetup status --target vdo pool
vdo: ERROR - VDO volume pool must be running

Any help would be greatly appreciated.

已采纳解答

原帖链接 · shodanshok · CC BY-SA 4.0

Growing a VDO physical device is a supported operation. The fact that you are not able to grow it, and not even stop it, can be related to the underlying device mapper table being out of sync.

If so, a full device restart should fix it.

摘自公开归档,保留原文语言,版式经整理,外部媒体与邮箱地址已移除。

资料来源与适用范围

资料来源
Server Fault
适用范围
以原帖系统、软件版本与发布日期为准(2020-06-10)
内容语言
中文;命令、路径和错误标识保留技术原文
本地收录日期
2026-11-15
授权说明
CC BY-SA 4.0

正文与所需资源由本站本地存储。查看来源及更新记录 ↗

请按适用版本和实际日志确认原因;本站没有对每一种系统或设备逐项执行文中的操作。