Linux LVM users
 help / color / mirror / Atom feed
From: Ed Tomlinson <tomlins@cam.org>
To: linux-lvm@sistina.com, Heinz Mauelshagen <mauelshagen@sistina.com>
Subject: Re: [linux-lvm] Request for misalignment tests
Date: Wed, 27 Jun 2001 06:56:52 -0400	[thread overview]
Message-ID: <01062706565200.00314@oscar> (raw)
In-Reply-To: <20010626161947.A11918@sistina.com>

On June 26, 2001 05:19 pm, Heinz Mauelshagen wrote:

oscar# pvdisplay -v /dev/hda3 | grep "^ *00000"
   00000 /dev/lv/swap              00086   4572
oscar# pvdisplay -v /dev/hde1 | grep "^ *00000"
   00000 /dev/lv/swap              00000   1136
oscar# pvdisplay -v /dev/hdg1 | grep "^ *00000"
   00000 /dev/lv/swap              00172   1137

oscar# pvdisplay /dev/hdg1
--- Physical volume ---
PV Name               /dev/hdg1
VG Name               lv
PV Size               37.28 GB / NOT usable 568 KB [LVM: 158 KB]
PV#                   3
PV Status             available
Allocatable           yes (but full)
Cur LV                2
PE Size (KByte)       4096
Total PE              9543
Free PE               0
Allocated PE          9543
PV UUID               v4eKca-DZfn-fYKP-q0pF-zWev-2HMM-TeKzbA

> All,
>
> we need your help in regard to the misalignment problems we are trying
> to fix right now in order to get facts concerning how many people are
> actually suffering from it.
>
>
> In case you created VGs or extended them with LVM 0.9.1 Beta 6 or 7,
> we'd appreciate if you could send us the output (if any) of
>
>    pvdisplay -v /dev/YourPVname | grep "^ *00000"
>
> if the sector offset in the last column is odd.
>
> If so, please add a "pvdisplay /dev/YourPVname" as well.
>
> We appreciate your help!
>
> Regards,
> Heinz      -- The LVM guy --
>
> =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=
>-=-
>
> Heinz Mauelshagen                                 Sistina Software Inc.
> Senior Consultant/Developer                       Bartningstr. 12
>                                                   64289 Darmstadt
>                                                   Germany
> Mauelshagen@Sistina.com                           +49 6151 7103 86
>                                                        FAX 7103 96
> =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=
>-=- _______________________________________________
> 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

  parent reply	other threads:[~2001-06-27 10:56 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-06-26 21:19 [linux-lvm] Request for misalignment tests Heinz Mauelshagen
2001-06-27  0:50 ` José Luis Domingo López
2001-06-27  5:11 ` Adrian Phillips
2001-06-27 10:56 ` Ed Tomlinson [this message]
2001-06-27 16:52 ` Jorg de Jong
2001-07-02 11:08   ` Heinz J. Mauelshagen
2001-07-02 14:18     ` Werner John
2001-07-03 10:01       ` Heinz J. Mauelshagen
2001-07-03 13:52         ` Ed Tomlinson
     [not found] <20010627220501.J31129@jensbenecke.de>
2001-06-30  6:00 ` Steven Lembark
2001-06-30  6:02 ` Steven Lembark

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=01062706565200.00314@oscar \
    --to=tomlins@cam.org \
    --cc=linux-lvm@sistina.com \
    --cc=mauelshagen@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