From mboxrd@z Thu Jan 1 00:00:00 1970 From: =?iso-8859-1?q?M=E5ns_Rullg=E5rd?= Message-ID: References: <20030828132053.C14441@uk.sistina.com> Mime-Version: 1.0 Content-Transfer-Encoding: 8bit Subject: [linux-lvm] Re: Recovering from disk failure Sender: linux-lvm-admin@sistina.com Errors-To: linux-lvm-admin@sistina.com Reply-To: linux-lvm@sistina.com List-Help: List-Post: List-Subscribe: , List-Unsubscribe: , List-Archive: Date: Thu Aug 28 13:53:02 2003 List-Id: Content-Type: text/plain; charset="utf-8" To: linux-lvm@sistina.com Alasdair G Kergon writes: >> Recently one of two disks in a volume group crashed, and I can't read >> it at all. Now, some LVs are entirely on the disk that survived. Is >> there any way I can just disable the broken LVs and continue using the >> complete ones? I'm using device-mapper and LVM2 > > Read the description of '--partial' on the lvm(8) man page. > e.g. (lv|vg)change -ay --partial I should have read the manuals before mailing. However, I still have some questions. Some LVs were split between the two disks. With the --partial option, it won't let me see them at all. Can I do something to get just read errors, or zeros, or whatever for the missing sectors? I could of course do some manual work with dd, but an automated method seems easier. > And '--removemissing' in vgreduce(8) to *permanently* destroy > the lost LVs (run with --test first to check what it will do). I don't want to do that until I've salvaged all the information I can get back. I have plenty of scratch space on other disks. -- M�ns Rullg�rd mru@users.sf.net