From mboxrd@z Thu Jan 1 00:00:00 1970 From: Anders Widman Message-Id: <77527890.20020228065139@tnonline.net> Subject: Re: [linux-lvm] filesystem corruption... In-Reply-To: <3399590000.1014862362@tiny> References: <224974437.20020227233630@tnonline.net> <20020227164228.A964@lynx.adilger.int> <3399590000.1014862362@tiny> MIME-Version: 1.0 Content-Transfer-Encoding: 7bit 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: Wed Feb 27 23:51:02 2002 List-Id: Content-Type: text/plain; charset="us-ascii" To: linux-lvm@sistina.com > On Wednesday, February 27, 2002 04:42:28 PM -0700 Andreas Dilger wrote: >> On Feb 27, 2002 23:36 +0100, Anders Widman wrote: >>> Unfortunatley, something went seriously wrong. I can't mount the disk >>> any more, or use reiserfsck. They (mount/reiserfsck) say there isn't >>> a valid filesystem on the device. Vgscan does however find all devices >>> and can activate the volume group, but reiserfsck doesn't work. >>> >>> What should I do to be able to save a s much data as possible? >> >> dd if=/dev/vg/lv of=/new/disk conv=sync,noerror > Then we should be able to use debugreiserfs and reiserfsck to > find a copy of the super in the log, or just recreate it. > -chris So. How much space would this require on the 'new' disk? The same amount as the entire LV? If that is, it would be impossible (for me, economically) to do this. The disk with bad blocks is 80GB, and I have a "spare" 80GB disk, but not more. //Anders