VDO Ghost Volume - Delete

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

VDO Ghost Volume - Delete

Post by penguinpages » 2019/11/07 18:14:42

I had a volume. Had user issue with it getting written over. Trying to rebuild. it is a Samsung 512GB SSD. /dev/disk/by-id/ata-Samsung_SSD_850_PRO_512GB_S250NXAGA15787L /sdc


# It removed ok
[root@thor ~]# vdo list
thor_vdo_bay2
thor_vdo_bay3
thor_vdo_bay4
thor_vdo_bay5
# wipe out data
[root@thor ~]# wipefs /dev/disk/by-id/ata-Samsung_SSD_850_PRO_512GB_S250NXAGA15787L
[root@thor ~]# dd if=/dev/zero of=/dev/disk/by-id/ata-Samsung_SSD_850_PRO_512GB_S250NXAGA15787L bs=1M count=10000
10000+0 records in
10000+0 records out
10485760000 bytes (10 GB) copied, 54.4928 s, 192 MB/s
[root@thor ~]# ls -al /dev/disk/by-id/
total 0
drwxr-xr-x 2 root root 600 Nov 5 14:53 .
drwxr-xr-x 6 root root 120 Nov 5 14:53 ..
lrwxrwxrwx 1 root root 9 Nov 5 14:52 ata-Hitachi_HTS545050B9SA02_110311PBL400M7JM1REV -> ../../sdf
lrwxrwxrwx 1 root root 9 Nov 5 14:52 ata-Samsung_SSD_850_PRO_512GB_S250NXAGA15787L -> ../../sdc
lrwxrwxrwx 1 root root 9 Nov 5 14:52 ata-ST9320325AS_5VD1Q5N7 -> ../../sda
lrwxrwxrwx 1 root root 9 Nov 5 14:52 ata-ST9500325AS_5VEAGVS2 -> ../../sde
lrwxrwxrwx 1 root root 9 Nov 5 14:52 ata-WDC_WDS100T2B0B-00YS70_19106A802926 -> ../../sdd
lrwxrwxrwx 1 root root 10 Nov 5 14:52 dm-name-centos_thor00-home -> ../../dm-2
lrwxrwxrwx 1 root root 10 Nov 5 14:52 dm-name-centos_thor00-root -> ../../dm-0
lrwxrwxrwx 1 root root 10 Nov 5 14:52 dm-name-centos_thor00-swap -> ../../dm-1
lrwxrwxrwx 1 root root 10 Nov 5 14:53 dm-name-thor_vdo_bay2 -> ../../dm-6
lrwxrwxrwx 1 root root 10 Nov 5 14:53 dm-name-thor_vdo_bay3 -> ../../dm-5
lrwxrwxrwx 1 root root 10 Nov 5 14:53 dm-name-thor_vdo_bay4 -> ../../dm-4
lrwxrwxrwx 1 root root 10 Nov 5 14:53 dm-name-thor_vdo_bay5 -> ../../dm-3
lrwxrwxrwx 1 root root 10 Nov 5 14:52 dm-uuid-LVM-ERCFyTJR17jbd1CvaRR1zug5uIhDIdKFdvrnyIhHE9gSwRHaT7yGs3LNBNDr33dG -> ../../dm-1
lrwxrwxrwx 1 root root 10 Nov 5 14:52 dm-uuid-LVM-ERCFyTJR17jbd1CvaRR1zug5uIhDIdKFFECXTf3Xz3FxPM8dI4pBqQLvjRCrw13t -> ../../dm-0
lrwxrwxrwx 1 root root 10 Nov 5 14:52 dm-uuid-LVM-ERCFyTJR17jbd1CvaRR1zug5uIhDIdKFVebbrQoF3C1yg8ip7cobVq3K70EsWCLf -> ../../dm-2
lrwxrwxrwx 1 root root 10 Nov 5 14:53 dm-uuid-VDO-0084e677-1a5e-496a-bf21-be3192449255 -> ../../dm-5
lrwxrwxrwx 1 root root 10 Nov 5 14:53 dm-uuid-VDO-38f279d7-d126-491d-8d06-fa214b2a4141 -> ../../dm-4
lrwxrwxrwx 1 root root 10 Nov 5 14:53 dm-uuid-VDO-3decc388-7a82-4a18-a464-c62389bcfb12 -> ../../dm-6
lrwxrwxrwx 1 root root 10 Nov 5 14:53 dm-uuid-VDO-c31bac6f-d4ed-460c-8f45-2e038c954eff -> ../../dm-3
lrwxrwxrwx 1 root root 10 Nov 5 14:52 lvm-pv-uuid-k2lVXe-Uk8x-Y81h-5e8W-sQfQ-rnVx-k5osGG -> ../../sdb2
lrwxrwxrwx 1 root root 9 Nov 5 14:52 usb-SanDisk_Cruzer_Blade_4C530000270911123325-0:0 -> ../../sdb
lrwxrwxrwx 1 root root 10 Nov 5 14:52 usb-SanDisk_Cruzer_Blade_4C530000270911123325-0:0-part1 -> ../../sdb1
lrwxrwxrwx 1 root root 10 Nov 5 14:52 usb-SanDisk_Cruzer_Blade_4C530000270911123325-0:0-part2 -> ../../sdb2
lrwxrwxrwx 1 root root 9 Nov 5 14:52 wwn-0x5000c5001bfe5489 -> ../../sda
lrwxrwxrwx 1 root root 9 Nov 5 14:52 wwn-0x5000c50024593ff4 -> ../../sde
lrwxrwxrwx 1 root root 9 Nov 5 14:52 wwn-0x5000cca67be4d887 -> ../../sdf
lrwxrwxrwx 1 root root 9 Nov 5 14:52 wwn-0x5001b448b847be41 -> ../../sdd
lrwxrwxrwx 1 root root 9 Nov 5 14:52 wwn-0x50025388400e2fab -> ../../sdc
[root@thor ~]# vdo create --name=thor_vdo_bay1 --device=/dev/disk/by-id/ata-Samsung_SSD_850_PRO_512GB_S250NXAGA15787L --activate=enabled --compression=enabled --deduplication=enabled --vdoLogicalSize=750G --writePolicy=async --verbose
Creating VDO thor_vdo_bay1
vdo: ERROR - VDO volume thor_vdo_bay1 already exists
[root@thor ~]# vdodumpconfig /dev/disk/by-id/ata-Samsung_SSD_850_PRO_512GB_S250NXAGA15787L
vdodumpconfig: allocateVDO failed for '/dev/disk/by-id/ata-Samsung_SSD_850_PRO_512GB_S250NXAGA15787L' with VDO Status: Bad magic number
vdodumpconfig: Could not load VDO from '/dev/disk/by-id/ata-Samsung_SSD_850_PRO_512GB_S250NXAGA15787L'
[root@thor ~]# vdodumpconfig thor_vdo_bay1
vdodumpconfig: Failed to make FileLayer from 'thor_vdo_bay1' with No such file or directory
vdodumpconfig: Could not load VDO from 'thor_vdo_bay1'
[root@thor ~]#


My guess it is left over somewhere in a configuation file for VDO. Any idea where this is stored?

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

Re: VDO Ghost Volume - Delete

Post by penguinpages » 2019/11/07 18:20:35

<sigh> Never mind..

Just need to try harder.

[root@thor var]# man vdo

<snip>
--confFile=file
-ffile
Specifies an alternate configuration file; the default is /etc/vdoconf.yml.

[root@thor var]# head -35 /etc/vdoconf.yml
####################################################################
# THIS FILE IS MACHINE GENERATED. DO NOT EDIT THIS FILE BY HAND.
####################################################################
config: !Configuration
vdos:
thor_vdo_bay1: !VDOService
_operationState: finished
ackThreads: 1
activated: enabled
bioRotationInterval: 64
bioThreads: 4
blockMapCacheSize: 128M
blockMapPeriod: 16380
compression: enabled
cpuThreads: 2
deduplication: enabled
device: /dev/disk/by-id/ata-Samsung_SSD_850_PRO_512GB_S250NXAGA15787L
hashZoneThreads: 1
indexCfreq: 0
indexMemory: 0.25
indexSparse: disabled
indexThreads: 0
logicalBlockSize: 4096
logicalSize: 1T
logicalThreads: 1
name: thor_vdo_bay1
physicalSize: 500107608K
physicalThreads: 1
readCache: disabled
readCacheSize: 0M
slabSize: 2G
writePolicy: async
thor_vdo_bay2: !VDOService
_operationState: finished

[root@thor var]# cp /etc/vdoconf.yml /tmp/

Remove section about that drive ..
Run create command now works

[root@thor var]# vdo create --name=thor_vdo_bay1 --device=/dev/disk/by-id/ata-Samsung_SSD_850_PRO_512GB_S250NXAGA15787L --activate=enabled --compression=enabled --deduplication=enabled --vdoLogicalSize=750G --writePolicy=async --verbose
Creating VDO thor_vdo_bay1
grep MemAvailable /proc/meminfo
pvcreate --config devices/scan_lvs=1 -qq --test /dev/disk/by-id/ata-Samsung_SSD_850_PRO_512GB_S250NXAGA15787L
blkid -p /dev/disk/by-id/ata-Samsung_SSD_850_PRO_512GB_S250NXAGA15787L
modprobe kvdo
vdoformat --uds-checkpoint-frequency=0 --uds-memory-size=0.25 --logical-size=750G /dev/disk/by-id/ata-Samsung_SSD_850_PRO_512GB_S250NXAGA15787L
vdodumpconfig /dev/disk/by-id/ata-Samsung_SSD_850_PRO_512GB_S250NXAGA15787L
Starting VDO thor_vdo_bay1
dmsetup status --target vdo thor_vdo_bay1
grep MemAvailable /proc/meminfo
modprobe kvdo
vdodumpconfig /dev/disk/by-id/ata-Samsung_SSD_850_PRO_512GB_S250NXAGA15787L
dmsetup create thor_vdo_bay1 --uuid VDO-4619a474-d352-4717-96ef-2fc3d75b322a --table '0 1572864000 vdo /dev/disk/by-id/ata-Samsung_SSD_850_PRO_512GB_S250NXAGA15787L 4096 disabled 0 32768 16380 on async thor_vdo_bay1 ack=1,bio=4,bioRotationInterval=64,cpu=2,hash=1,logical=1,physical=1'
dmsetup status --target vdo thor_vdo_bay1
Starting compression on VDO thor_vdo_bay1
dmsetup message thor_vdo_bay1 0 compression on
vdodmeventd -r thor_vdo_bay1
dmsetup status --target vdo thor_vdo_bay1
VDO instance 4 volume is ready at /dev/mapper/thor_vdo_bay1
[root@thor var]#


Sorry for forum banter.

Post Reply

Return to “CentOS 7 - General Support”