![]() This server just has disk bays so I try to make it logical that I label the block device to "server_bay#" so errors correlate more for me. and after every possible way I can think of to wipe it. This device you're attempting to put VDO on top of is an mpath device? I struggle to say this is VDO now in that I can't create even ext file system on it, but I assumed it was VDO issue (or prep command VDO calls of pvcreate). # mlock_filter = # cat /etc/redhat-release # Configuration option activation/mlock_filter. # filtering settings: component filters such as multipath and MD This does not apply to other, non-regexp, lvmetad always keeps unfiltered information # by pvscan -cache), devices/filter is ignored and all devices are The LVs are ignored using a built in device filter that # filtered), which can cause performance problems on systems with # This is a quick way of filtering out block devices that are not # The results of filtering are cached on disk to avoid rescanning dud # The syntax is the same as devices/filter. # Use global_filter to hide devices from these LVM system components. # not suitable for system-wide device filtering, e.g. # Because devices/filter may be overridden from the command line, it is # Configuration option devices/global_filter. # See the use_lvmetad comment for a special case regarding filters. # Run vgscan after changing the filter to regenerate the cache. # is used to drive LVM filtering like MD component detection, multipath TEST MODE: Metadata will NOT be updated and volumes will not be (de)activated.ĭevice /dev/disk/by-id/ata-SAMSUNG_SSD_PM851_mSATA_512GB_S1EWNYAF609306 excluded by a ~]# grep filter /etc/lvm/lvm.conf dev/sdb: calling ioclt to re-read partition table: ~]# ~]# lsblk -a dev/sdb: 2 bytes were erased at offset 0x000001fe (dos): 55 aa Wipefs: error: /dev/sdb: probing initialization failed: Device or resource ~]# wipefs -a /dev/sdb -force └─centos_odin-home 253:7 0 17.2G 0 lvm ~]# wipefs /dev/sdbĠx1fe dos # wipefs -a /dev/sdb dev/sdb1 is apparently in use by the system will not make a filesystem ~]# lsblk -a The partition table has been altered! Calling ioctl() to re-read partition table. Partition 1 of type Linux and of size 477 GiB is set I/O size (minimum/optimal): 512 bytes / 512 bytes ![]() Sector size (logical/physical): 512 bytes / 512 bytes if I could format with regular file system but it won't ~]# fdisk /dev/sdbĬhanges will remain in memory only, until you decide to write them.īe careful before using the write command.ĭevice does not contain a recognized partition tableīuilding a new DOS disklabel with disk identifier 0xbcff3e20.ĭisk /dev/sdb: 512.1 GB, 512110190592 bytes, 1000215216 sectors ![]() Lots of hits on google about this "excluded by a filter." message but no answers that make sense or answers to posts. I attempted many clean up attempts and even gave reboot a try. Vdo: ERROR - Device /dev/disk/by-id/ata-SAMSUNG_SSD_PM851_mSATA_512GB_S1EWNYAF609306 excluded by a ~]# Pvcreate -config devices/scan_lvs=1 -qq -test /dev/disk/by-id/ata-SAMSUNG_SSD_PM851_mSATA_512GB_S1EWNYAF609306 First step was to remove Windows Partitions (and even ran dd of /dev/zero to drive) and then lay down ~]# vdo create -name=odin_vdo_bay1 -device=/dev/disk/by-id/ata-SAMSUNG_SSD_PM851_mSATA_512GB_S1EWNYAF609306 -activate=enabled -compression=enabled -deduplication=enabled -vdoLogicalSize=750G -writePolicy=async -verbose Installed a new one and now trying to format it for use. I needed to upgrade a drive and so pulled it out. I have a posting to CentOS Community forum here: I don't know if this is a VDO issue or some subordinate step VDO uses when it creates a new volume.
0 Comments
Leave a Reply. |