Linux LVM users
 help / color / mirror / Atom feed
From: IpSo <ipso@snappymail.ca>
To: linux-lvm@sistina.com
Subject: Re: [linux-lvm] A way to bypass LVM and extract the raw data off?
Date: Tue Jan  8 21:03:01 2002	[thread overview]
Message-ID: <1010545378.3c3bb2e2a4dec@www.snappymail.ca> (raw)
In-Reply-To: <20020109023404.GC1096@auctionwatch.com>

Quoting Petro <petro@auctionwatch.com>:

> On Tue, Jan 08, 2002 at 06:26:36PM -0800, IpSo wrote:
> > Well, it doesn't look like there is a way I can recover my LVM volume
> groups and
> > whatnot. (See below) But I know theres a fully intact ReiserFS of 17315mb
> on
> > /dev/hda6. "gpart" scanned my disk and came up with this: 
> 
>     Does the OS recognize /dev/hda6 as a partition? 


Yup! I'm confident everything as far as the reiser filesystem is fine, just LVM
is very confused. 

   Device Boot    Start       End    Blocks   Id  System
/dev/hda1   *         1       507    255496+  82  Linux swap
/dev/hda2           508     39813  19810224    5  Extended
/dev/hda5           508      4633   2079472+  83  Linux
/dev/hda6          4634     39813  17730688+  8e  Linux LVM

 

> 
> > Is there some way to "dd" the data off onto another partition and access
> it
> > there? Because I know the filesystem was only on a single PV, and a single
> LV,
> > and the problems occured when trying to extend that LV, but I never got to
> the
> > point of extending the filesystem itself with reiser_resize. You would
> think I
> > could somehow using the offsets given above create a new partition to copy
> the
> > data to, run a reiserfsck and rebuild the file system so I can access the
> data?
> > Has anyone tryed something along these lines before?
> 
>     If you have the HD space, you could try dd if=/dev/hda6
>     of=/some/file
> 
>     Then mount -o loop /some/file /mnt/point -t reiserfs. 
> 
>     I don't think this would do any more damage. 
> 
I'll give it a shot I guess, won't this loopback file contain the extra LVM
information and cause problems when trying to mount it though? Does the LVM
information take up the first 2mb or something that I could set the offset as,
so it doesn't carry over to the loopback file?

> -- 
> Share and Enjoy. 
> 
> _______________________________________________
> 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
> 


IpSo

--------------------------------------------------------------------
Never worry about viruses in your Email again.
Get your FREE! virus scanned Email accounts at http://snappymail.ca

  reply	other threads:[~2002-01-08 21:03 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-01-06  3:33 [linux-lvm] VG dissappeared without a trace? IpSo
2002-01-06 13:03 ` IpSo
2002-01-06 16:22   ` Andreas Dilger
2002-01-06 17:29     ` IpSo
2002-01-08 20:27       ` [linux-lvm] A way to bypass LVM and extract the raw data off? IpSo
2002-01-08 20:35         ` Petro
2002-01-08 21:03           ` IpSo [this message]
2002-01-09 13:41             ` Andreas Dilger
2002-01-09 15:44               ` IpSo
2002-01-09 16:26                 ` Andreas Dilger
2002-01-09 17:26                   ` IpSo
2002-01-08 21:05         ` Andreas Dilger
2002-01-09  9:02           ` IpSo
2002-01-09 10:30             ` Holger Grothe
2002-01-09 12:04               ` IpSo

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=1010545378.3c3bb2e2a4dec@www.snappymail.ca \
    --to=ipso@snappymail.ca \
    --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