Received: from mx1.redhat.com (mx1.redhat.com [172.16.48.31]) by int-mx1.corp.redhat.com (8.11.6/8.11.6) with ESMTP id k21Eee126249 for ; Wed, 1 Mar 2006 09:40:40 -0500 Received: from emx.vniitf.ru (emx.vniitf.ru [212.57.149.10]) by mx1.redhat.com (8.12.11/8.12.11) with ESMTP id k21EeZhW024317 for ; Wed, 1 Mar 2006 09:40:36 -0500 Received: from exim by emx.vniitf.ru with antivirus-scanned (Exim 3.33 #1) id 1FESVh-0001QI-00 for linux-lvm@redhat.com; Wed, 01 Mar 2006 19:41:01 +0500 Received: from c-212-57-149-57.dialup.snz.ru ([212.57.149.57]) by emx.vniitf.ru with esmtp (Exim 3.33 #1) id 1FESVh-0001QA-00 for linux-lvm@redhat.com; Wed, 01 Mar 2006 19:41:01 +0500 Message-ID: <4405B25F.5090001@mail.snz.ru> Date: Wed, 01 Mar 2006 19:40:31 +0500 From: Sid MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Subject: [linux-lvm] LVM metadata recovery test Reply-To: LVM general discussion and development List-Id: LVM general discussion and development List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , List-Id: Content-Type: text/plain; charset="us-ascii" To: linux-lvm@redhat.com Hi all, Does anybody know how to artificially injure VG metadatata ? The purpose is to prove LVM recovery capabilities. IDima