[Vdo-devel] vdo + lvm cache case vdo failed

Dennis Keefe dkeefe at redhat.com
Tue Apr 9 11:52:56 UTC 2019


Interesting.  Would you mind providing the kernel version and package
version for vdo and kmod-vdo?

On Tue, Apr 9, 2019, 4:18 AM 劼磊周 <loli.miko at gmail.com> wrote:

> hello:
>
>  Today i try to use lvm cache on vdo device
>
> i use the command
>
> pvcreate /dev/sdb
> pvcreate /dev/mapper/image_store
> vgcreate image /dev/sdb
> vgextend image /dev/mapper/image_store
> lvcreate -l 20G -n meta image /dev/sdb
> lvcreate -l 100%FREE -n cache image /dev/sdb
> lvconvert --type cache-pool --poolmetadata image/meta image/cache
>
> lvcreate -l 100%FREE -n data image /dev/mapper/image_store
> lvconvert --type cache --cachepool image/cache --cachemode writeback
> image/data
> mkfs.xfs -K /dev/mapper/image-data
> mount /dev/mapper/image-data /exports/disk0/
>
> in my case sdb is ssd device
> /dev/mapper/image_store  is a vdo device
>
> Everything look fine after reboot.
>
> We i reboot server. Vdo device cannot be start.
>
> vdo: utils.FileLock: DEBUG - attempting to lock
> /run/lock/vdo/_etc_vdoconf.yml.lock in 20s mode exclusive
> vdo: utils.FileLock: DEBUG - attempting to lock
> /run/lock/vdo-config-singletons mode exclusive
> vdo: vdo.vdomgmnt.Configuration: DEBUG - Reading configuration from
> /etc/vdoconf.yml
> vdo: utils.FileLock: DEBUG - released lock /run/lock/vdo-config-singletons
> vdo: vdo.vdomgmnt.Service.VDOService: INFO - Starting VDO image_store
> Starting VDO image_store
> vdo: vdo.vdomgmnt.Service.VDOService: DEBUG - No failure requiring
> recovery for VDO volume image_store
> vdo: utils.Command: DEBUG - dmsetup: command failed, exit status 1
> vdo: utils.Command: DEBUG - stdout:
> vdo: utils.Command: DEBUG - stderr: Device does not exist.
> Command failed.
> vdo: utils.Command: DEBUG - grep: command succeeded
> vdo: utils.Command: DEBUG - stdout: MemAvailable:   130560288 kB
> vdo: utils.Command: DEBUG - stderr:
> vdo: utils.Command: DEBUG - modprobe: command succeeded
> vdo: utils.Command: DEBUG - stdout:
> vdo: utils.Command: DEBUG - stderr:
> vdo: utils.Command: DEBUG - vdodumpconfig: command failed, exit status 1
> vdo: utils.Command: DEBUG - stdout:
> vdo: utils.Command: DEBUG - stderr: vdodumpconfig: allocateVDO failed for
> '/dev/disk/by-id/scsi-364cd98f05bc87f00242af26c0b2df932' with VDO Status:
> Bad magic number
> vdodumpconfig: Could not load VDO from
> '/dev/disk/by-id/scsi-364cd98f05bc87f00242af26c0b2df932'
> vdo: vdo.vdomgmnt.Service.VDOService: ERROR - Could not set up device
> mapper for image_store
> vdo: vdo.vdomgmnt.Configuration: DEBUG - Configuration is clean, not
> persisting
> vdo: utils.FileLock: DEBUG - released lock
> /run/lock/vdo/_etc_vdoconf.yml.lock
> vdo: vdo: ERROR - vdodumpconfig: allocateVDO failed for
> '/dev/disk/by-id/scsi-364cd98f05bc87f00242af26c0b2df932' with VDO Status:
> Bad magic number
>
> Bad magic number  ERROR was be shown.
>
>  Thanks
>
> --
>                                                           leon.zhou
>
> _______________________________________________
> Vdo-devel mailing list
> Vdo-devel at redhat.com
> https://www.redhat.com/mailman/listinfo/vdo-devel
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://listman.redhat.com/archives/vdo-devel/attachments/20190409/2257f29d/attachment.htm>


More information about the vdo-devel mailing list