All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Kirby C. Bohling" <kbohling@birddog.com>
To: linux-lvm@sistina.com
Subject: Re: [linux-lvm] accidently formatted a physical volume...
Date: Mon Aug 19 15:58:02 2002	[thread overview]
Message-ID: <3D6159EA.1070406@birddog.com> (raw)
In-Reply-To: 20020819205005.GA26781@grimlock

Start by using dd or something to get an original image of the drive 
before anything else bad is done to it.  Copy it off to another drive, 
copy to tape.  Personally, I'd copy it to a big filesystem (if it 
supports bigger then 2 GB), and see if you can mount it loopback.  I 
know I read on the LKML a guy mounted several filesytems that way that 
were considerablely larger then 2GB.

With the backup, when something goes wrong you can always start over 
fresh without worring about the undoing your original attempts.

I'd imagine that doing a vgcfgrestore to the device, followed by 
mounting the filesystem without fsck'ing it will get you some data. 
Running fsck on it afterwards and see what else you can get.  Do *_NOT_* 
try that without a backup of the original media.  Your big problem is 
that you're going to have superblocks and inode tables written right in 
the middle of your drive other then that, everything should be on the 
disk right where you left it.

I had a friend who just lost an ext2 drive due to a power surge the 
other day, fscking it was destorying the filesystem, just mounting it 
and running tar got us 90% of the data.  Fortuantely the other 10% came 
off a RH CD so it was no problem.

	Thanks,
		Kirby

Adam McDaniel wrote:
> On Mon, Aug 19, 2002 at 10:41:24PM +0200, Anders Widman wrote:
> 
>>>>Or, is there any way that I can fix/restore the formatted drive?
>>>
>>>Not at the *NIX level. If the data were SERIOUSLY valuable
>>>it can be recovered by physical means. Short of that I'd
>>>say it's time to reach for your tapes...
>>
> 
> The unfortunate thing was that timing couldn't have been worse. The
> last backup I made before the incident would only contain a fraction
> of the info that I actually need. Partly my fault, I know, but being
> able to restore the drive would be the goal.
> 
> 
>>Are you sure? The data should be there in the co-worker did not make a
>>"full" (zeroing blocks) format. Is it not possible to restore the LVM
>>headers (or what it is called) on that drive?
> 
> 
> I do know that it was a straight simple format, literally
> 'mkfs.ext2 /dev/hdb', so I know the info is still there. My experience
> in this is rather limited, so I'm not sure of the best way to fish it
> out.
> 

  reply	other threads:[~2002-08-19 15:58 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-08-19 14:23 [linux-lvm] accidently formatted a physical volume Adam McDaniel
2002-08-19 14:38 ` Steven Lembark
     [not found]   ` <284650000.1029786116@[192\.168\.200\.4]>
2002-08-19 15:42     ` Anders Widman
2002-08-19 15:50       ` Adam McDaniel
2002-08-19 15:58         ` Kirby C. Bohling [this message]
2002-08-20 12:56           ` Adam McDaniel
2002-08-20 13:29             ` Kirby C. Bohling
2002-08-20 13:55               ` Andreas Dilger

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=3D6159EA.1070406@birddog.com \
    --to=kbohling@birddog.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.