From: "Heinz J . Mauelshagen" <mauelshagen@sistina.com>
To: linux-lvm@sistina.com
Subject: Re: [linux-lvm] pvdisplay/lvdisplay discrepancy
Date: Mon Dec 9 12:16:00 2002 [thread overview]
Message-ID: <20021209190238.B20282@sistina.com> (raw)
In-Reply-To: <1039450746.14457.11.camel@benway.cv.telegroup.com>; from acox@ia.primustel.com on Mon, Dec 09, 2002 at 10:19:07AM -0600
On Mon, Dec 09, 2002 at 10:19:07AM -0600, Aran Cox wrote:
> Thanks for sending me those binaries but unfortunately they produce the
> same output.
Odd :(
Then send your metadata to me directly (mge@sistina.com) for further
investigation please.
Do a "dd if=/dev/$DEV of=$DEV.vgda count=4k bs=1k" where DEV is sdb, hde4 etc.
(IOW: all you PVs belonging to the VG in question)
Archive these .vgda files with tar, bzip2 the archive and send that
email-attached.
Regards,
Heinz -- The LVM Guy --
>
> Thanks again,
> Aran
>
> On Mon, 2002-12-09 at 04:46, Heinz J . Mauelshagen wrote:
> > Alan,
> >
> > I am not sure if there's a difference between the Redhat package and our source
> > causing this.
> > Are you able to reproduce this with stock LVM1.0.6 tools from www.sistina.com ?
> > (have send pvdisplay and lvdisplay version 1.0.6 in private email to you
> > to test this).
> >
> > Get back to me if there is none and I'll have a look at your metadata.
> >
> > Regards,
> > Heinz -- The LVM Guy --
> >
> >
> > On Fri, Dec 06, 2002 at 10:28:18PM -0600, Aran Cox wrote:
> > > I've discovered that pvdisplay and lvdisplay seem to disagree on the
> > > exact location of some extents in a volume group on my system.
> > >
> > > I am using stock 2.4.19 kernel with the lvm tools from the RPM package
> > > of the same name for RH7.3.
> > >
> > > I'll show the output of the *display programs below but to summarize:
> > > pvdisplay shows a small number of extents in /dev/main/var as being on
> > <SNIP>
> > > "/dev/sdb"
> > >
> > >
> > >
> > >
> > > _______________________________________________
> > > linux-lvm mailing list
> > > linux-lvm@sistina.com
> > > http://lists.sistina.com/mailman/listinfo/linux-lvm
> > > read the LVM HOW-TO at http://tldp.org/HOWTO/LVM-HOWTO/
> >
> > *** Software bugs are stupid.
> > Nevertheless it needs not so stupid people to solve them ***
> >
> > linux-lvm mailing list
> > linux-lvm@sistina.com
> > http://lists.sistina.com/mailman/listinfo/linux-lvm
> > read the LVM HOW-TO at http://tldp.org/HOWTO/LVM-HOWTO/
> --
> Aran Cox <acox@ia.primustel.com>
> Primus Telecommunications - Network Engineering
>
>
> _______________________________________________
> linux-lvm mailing list
> linux-lvm@sistina.com
> http://lists.sistina.com/mailman/listinfo/linux-lvm
> read the LVM HOW-TO at http://tldp.org/HOWTO/LVM-HOWTO/
*** 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
=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
prev parent reply other threads:[~2002-12-09 12:16 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-12-06 23:48 [linux-lvm] pvdisplay/lvdisplay discrepancy Aran Cox
2002-12-09 4:54 ` Heinz J . Mauelshagen
2002-12-09 10:19 ` Aran Cox
2002-12-09 12:16 ` Heinz J . Mauelshagen [this message]
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=20021209190238.B20282@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 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.