VDO Recreate Error

General support questions
Post Reply
User avatar
penguinpages
Posts: 66
Joined: 2015/07/21 13:58:05

VDO Recreate Error

Post by penguinpages » 2019/09/30 13:28:41

I have a 1TB SSD. Running for a few weeks now as VDO volume to be joined under Gluster (once I got that fixed :P )

But I noticed i fat fingered the size and instead of my desired 3:1 ratio over subscription... 3000G. I set it to 30000G

I stopped it and removed it fine.

When I went to create I got error "No such file or directory: ''


####
[root@odin ~]# vdo create --name=odin_vdo_bay2 --device=/dev/sde --activate=enabled --compression=enabled --deduplication=enabled --vdoLogicalSize=3000G --writePolicy=async --verbose -force --verbose
Creating VDO odin_vdo_bay2
grep MemAvailable /proc/meminfo
pvcreate --config devices/scan_lvs=1 -qq --test /dev/sde
blkid -p /dev/sde
modprobe kvdo
vdo: ERROR - [Errno 2] No such file or directory: ''
[root@odin ~]#
[root@odin ~]#
[root@odin ~]# vdo create --name=odin_vdo_bay2 --device=/dev/sde --activate=enabled --compression=enabled --deduplication=enabled --vdoLogicalSize=3000G --writePolicy=async --verbose -force --verbose
Creating VDO odin_vdo_bay2
vdo: ERROR - VDO volume odin_vdo_bay2 previous operation (create) is incomplete; recover by performing 'remove --force'
[root@odin ~]# uname -a
Linux odin.penguinpage.local 3.10.0-1062.1.1.el7.x86_64 #1 SMP Fri Sep 13 22:55:44 UTC 2019 x86_64 x86_64 x86_64 GNU/Linux
[root@odin ~]# rpm -qa |grep vdo
vdo-6.1.2.41-4.el7.x86_64
kmod-kvdo-6.1.2.41-5.el7.x86_64


Assumed something not fully cleaned up on volume so did "wipefs /dev/disk/by-id/ata-WDC_WDS100T2B0B-00YS70_183533804564"

Tried to re-create and same error. Reboot and
[root@odin ~]# vdo list
odin_vdo_bay1
odin_vdo_bay3
odin_vdo_bay4
odin_vdo_bay5
[root@odin ~]# vdo create --name=odinvdo_bay2 --device=/dev/sde --activate=enabled --compression=enabled --deduplication=enabled --vdoLogicalSize=3000G --writePolicy=async --verbose -force --verbose
Creating VDO odinvdo_bay2
vdo: ERROR - Device /dev/sde already configured for VDO use
[root@odin ~]# vdo start -n odinvdo_bay2
vdo: ERROR - VDO volume odinvdo_bay2 not found
[root@odin ~]#

Try to get a dump of vdo of volume (/dev/sde is the SSD volume .. I have another one /dev/sdf which is working fine)
[root@odin ~]# vdodumpconfig /dev/sde
vdodumpconfig: allocateVDO failed for '/dev/sde' with VDO Status: Bad magic number
vdodumpconfig: Could not load VDO from '/dev/sde'
[root@odin ~]# vdodumpconfig /dev/sdf
VDOConfig:
blockSize: 4096
logicalBlocks: 786432000
physicalBlocks: 244190646
slabSize: 524288
recoveryJournalSize: 32768
slabJournalBlocks: 224
UUID: cc31e38b-6ace-4c4a-979e-ad3530be27d4
[root@odin ~]#

Tried to re-format volume
[root@odin ~]# vdoformat /dev/sde
Logical blocks defaulted to 242805445 blocks[root@odin ~]#


Trying to track down the steps and sequence to use VDO and repair things. Wish there was published set of debug steps ... lots of hits in kenel bugs but not sure how related they are to this. I am assuming this is user / process error and not a bug.

User avatar
penguinpages
Posts: 66
Joined: 2015/07/21 13:58:05

Re: VDO Recreate Error

Post by penguinpages » 2019/09/30 20:32:25

I would love to post here what I did to fix this.. but for me to say "reboot" is lame... but... somewhere along the way to poke at this via mounts / formats / wipefs // and... reboot..

It is now working


[root@odin gv1]# vdo create --name=odin_vdo_bay2 --device=/dev/sdd --activate=enabled --compression=enabled --deduplication=enabled --vdoLogicalSize=3000G --writePolicy=async --verbose --force
Creating VDO odin_vdo_bay2
grep MemAvailable /proc/meminfo
modprobe kvdo
vdoformat --uds-checkpoint-frequency=0 --uds-memory-size=0.25 --logical-size=3000G --force /dev/disk/by-id/ata-WDC_WDS100T2B0B-00YS70_183533804564
vdodumpconfig /dev/disk/by-id/ata-WDC_WDS100T2B0B-00YS70_183533804564
Starting VDO odin_vdo_bay2
dmsetup status --target vdo odin_vdo_bay2
grep MemAvailable /proc/meminfo
modprobe kvdo
vdodumpconfig /dev/disk/by-id/ata-WDC_WDS100T2B0B-00YS70_183533804564
dmsetup create odin_vdo_bay2 --uuid VDO-a7d86d0e-e4d6-44ba-8e51-64e3cc19e13c --table '0 6291456000 vdo /dev/disk/by-id/ata-WDC_WDS100T2B0B-00YS70_183533804564 4096 disabled 0 32768 16380 on async odin_vdo_bay2 ack=1,bio=4,bioRotationInterval=64,cpu=2,hash=1,logical=1,physical=1'
dmsetup status --target vdo odin_vdo_bay2
Starting compression on VDO odin_vdo_bay2
dmsetup message odin_vdo_bay2 0 compression on
vdodmeventd -r odin_vdo_bay2
dmsetup status --target vdo odin_vdo_bay2
VDO instance 4 volume is ready at /dev/mapper/odin_vdo_bay2
[root@odin gv1]# vdo list
odin_vdo_bay1
odin_vdo_bay2
odin_vdo_bay3
odin_vdo_bay4
odin_vdo_bay5
[root@odin gv1]#


I will post if I find a more intelligent way to help others root cause.

Post Reply

Return to “CentOS 7 - General Support”