From: Andreas Dilger <adilger@turbolabs.com>
To: Timshel Knoll <timshel@pobox.com>
Cc: linux-lvm@sistina.com
Subject: Re: [linux-lvm] Fixing corrupted LVM PV headers?
Date: Fri Jan 4 14:08:03 2002 [thread overview]
Message-ID: <20020104131028.O12868@lynx.no> (raw)
In-Reply-To: <5.1.0.14.0.20020105005533.00bb8c28@pop.ihug.com.au>; from timshel@pobox.com on Sat, Jan 05, 2002 at 01:12:09AM +1100
On Jan 05, 2002 01:12 +1100, Timshel Knoll wrote:
> At 02:27 PM 3/01/2002 -0700, Andreas Dilger wrote:
> >Well, this seems to become my specialty:
> >
> >- Look in include/linux/lvm.h for descriptions of the LVM metadata (see
> > pv_disk_t, lv_disk_t, vg_disk_t, etc)
> >... etc
>
> Thanks, this is exactly what I was looking for. I will try this over the next
> few days and let you know how it went. Just need to find a web copy of
> the kernel sources - mine were on my LVM /usr filesystem ... ;-/
> Oh the irony ...
Well, the sistina site has CVSWeb for browsing the LVM sources. Use that.
Cheers, Andreas
--
Andreas Dilger
http://sourceforge.net/projects/ext2resize/
http://www-mddsp.enel.ucalgary.ca/People/adilger/
next prev parent reply other threads:[~2002-01-04 14:08 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-01-03 11:30 [linux-lvm] Fixing corrupted LVM PV headers? timshel
2002-01-03 15:25 ` Andreas Dilger
2002-01-04 8:11 ` Timshel Knoll
2002-01-04 14:08 ` Andreas Dilger [this message]
2002-01-05 10:43 ` Timshel Knoll
2002-01-05 11:54 ` Timshel Knoll
2002-01-05 18:01 ` Andreas Dilger
2002-01-08 12:20 ` [linux-lvm] NEED HELP ON VGDA!! Prashant Kharche
2002-01-08 12:32 ` Andreas Dilger
2002-01-09 3:16 ` Joe Thornber
2002-01-08 13:37 ` mitch
2002-01-08 13:49 ` [linux-lvm] LVM on large drives David Orman
2002-01-08 16:24 ` Petro
2002-01-12 18:11 ` [linux-lvm] ERROR "pv_read(): PV identifier invalid David Orman
2002-01-13 4:54 ` Goetz Bock
2002-01-13 10:53 ` Glenn Shannon
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=20020104131028.O12868@lynx.no \
--to=adilger@turbolabs.com \
--cc=linux-lvm@sistina.com \
--cc=timshel@pobox.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