Hi list, deactivating the whole vg with vgchange -an dmivg resulted a working lvconvert --repair dmivg/winthinpool after this, i was able to remove the "old" metadata on /dev/ram0 with lvremove /dev/mapper/dmivg-winthinpoo_meta0 After this, i was able to reduce the vg with vgreduce dmivg /dev/ram0 DONE So all is fine now. Regards Oliver On 14.05.2017 19:00, Oliver Rath wrote: > Hi list, > > Ive moved the _tmeta part of a thinpool to a (ramdisk) device for > testing and wanted now to move it back to disk, but this fail: > > # pvmove -v -n /dev/mapper/dmivg-winthinpool_tmeta /dev/ram0 /dev/sdg1 > WARNING: Failed to connect to lvmetad. Falling back to device scanning. > Cluster mirror log daemon not included in build. > Wiping internal VG cache > Wiping cache of LVM-capable devices > Archiving volume group "dmivg" metadata (seqno 217). > Creating logical volume pvmove0 > Moving 229 extents of logical volume dmivg/winthinpool_tmeta > activation/volume_list configuration setting not defined: Checking > only host tags for dmivg/winthinpool_tmeta. > Setting up pvmove in on-disk volume group metadata. > Creating dmivg-pvmove0 > device-mapper: create ioctl on dmivg-pvmove0 > LVM-EHcvL2Ube7wb2effdgOufgqLTeAS9K6fABDshfurJLvBuIPvuBMXLnlfGxHUNCc8 > failed: Device or resource busy > Failed to suspend winthinpool_tmeta > ABORTING: Temporary pvmove mirror activation failed. > > > It seems, that pvmove is trying to create a mirror-device from *_tmeta > on the target disk, but this seems to fail. > > The computer is still running, so do I have a possibility to save the > situation? Can I transfer the *tmeta in another way? > > LVM und Thin-provisioning-tools are from git today. > > Tfh! > Oliver > _______________________________________________ linux-lvm mailing list linux-lvm@redhat.com https://www.redhat.com/mailman/listinfo/linux-lvm read the LVM HOW-TO at http://tldp.org/HOWTO/LVM-HOWTO/
