Linux LVM users
 help / color / mirror / Atom feed
From: "Heinz J . Mauelshagen" <mauelshagen@sistina.com>
To: linux-lvm@sistina.com
Subject: Re: [linux-lvm] filesystem corruption...
Date: Thu Feb 28 03:01:01 2002	[thread overview]
Message-ID: <20020228100118.A25011@sistina.com> (raw)
In-Reply-To: <45423062.20020228093553@tnonline.net>; from andewid@tnonline.net on Thu, Feb 28, 2002 at 09:35:53AM +0100

On Thu, Feb 28, 2002 at 09:35:53AM +0100, Anders Widman wrote:
> 
> >> On Wednesday, February 27, 2002 04:42:28 PM -0700 Andreas Dilger <adilger@clusterfs.com> 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
> 
> Oh, I forgot to ask how I can recover the filsystem
> header/suprtblock.. What exactly is "dd if=/dev/vg/lv of=/new/disk
> conv=sync,noerror" doing to the data, except copying it to the new
> device?

It copies all it can read to another sane device so that youe don't loose
more data if your drive turns worse.

After that, you want to use "reiserfsck --rebuild-sb /dev/vg/lv".


> 
> //Anders
> 
> 
> _______________________________________________
> linux-lvm mailing list
> linux-lvm@sistina.com
> http://lists.sistina.com/mailman/listinfo/linux-lvm
> read the LVM HOW-TO at http://www.sistina.com/lvm/Pages/howto.html

-- 

Regards,
Heinz    -- The LVM Guy --

*** Software bugs are stupid.
    Nevertheless it needs not so stupid people to solve them ***

=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-

Heinz Mauelshagen                                 Sistina Software Inc.
Senior Consultant/Developer                       Am Sonnenhang 11
                                                  56242 Marienrachdorf
                                                  Germany
Mauelshagen@Sistina.com                           +49 2626 141200
                                                       FAX 924446
=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-

  reply	other threads:[~2002-02-28  3:01 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-02-27 16:36 [linux-lvm] filesystem corruption Anders Widman
2002-02-27 17:42 ` Andreas Dilger
2002-02-27 20:13   ` Chris Mason
2002-02-27 23:51     ` Anders Widman
2002-02-28  2:35       ` Anders Widman
2002-02-28  3:01         ` Heinz J . Mauelshagen [this message]
2002-02-28  3:07           ` Anders Widman
2002-03-01  3:59             ` Heinz J . Mauelshagen
2002-03-01  7:25               ` Anders Widman

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20020228100118.A25011@sistina.com \
    --to=mauelshagen@sistina.com \
    --cc=linux-lvm@sistina.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox