From: Anders Widman <andewid@tnonline.net>
To: linux-lvm@sistina.com
Subject: Re: [linux-lvm] filesystem corruption...
Date: Thu Feb 28 02:35:03 2002 [thread overview]
Message-ID: <45423062.20020228093553@tnonline.net> (raw)
In-Reply-To: <77527890.20020228065139@tnonline.net>
>> 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?
//Anders
next prev parent reply other threads:[~2002-02-28 2:35 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 [this message]
2002-02-28 3:01 ` Heinz J . Mauelshagen
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=45423062.20020228093553@tnonline.net \
--to=andewid@tnonline.net \
--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