> For the record: finally, I edited the last metadata-backup, put the > successfully mirrored segment on the raid into the LV (instead of the > pvmovesomething mirror), removed references to pvmove, the damaged PV > and the "homevideo" LV, vgcfgrestored the config, rebooted, and > everything works. > > Robert It's good to know what kind of thing can actually work in practice. I'm absent minded, the kind of guy who says "oops" a lot, so it's always good to know ways of recovering. -- Ray Morris support@bettercgi.com Strongbox - The next generation in site security: http://www.bettercgi.com/strongbox/ Throttlebox - Intelligent Bandwidth Control http://www.bettercgi.com/throttlebox/ Strongbox / Throttlebox affiliate program: http://www.bettercgi.com/affiliates/user/register.php On Wed, 14 Sep 2011 09:23:22 +0200 Robert Schöftner <rmu@unfoo.net> wrote: > Am 2011-09-13 00:15, schrieb Robert Schöftner: > > my plan is to edit the latest archived meta-data, remove the > > pvmove-mirror, exchange the segment pointing to the missing device > > with the mirrored segment, and vcfgrestore it, if no better idea > > comes up. the saved metadata confirms that the segment belonging to > > LV "shares" was completely mirrored before the harddisk died, so > > all the needed data is there. > For the record: finally, I edited the last metadata-backup, put the > successfully mirrored segment on the raid into the LV (instead of the > pvmovesomething mirror), removed references to pvmove, the damaged PV > and the "homevideo" LV, vgcfgrestored the config, rebooted, and > everything works. > > Robert > > _______________________________________________ > 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/ > _______________________________________________ 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/
