Linux LVM users
 help / color / mirror / Atom feed
From: Heinz Mauelshagen <mauelshagen@redhat.com>
To: linux-lvm@redhat.com
Subject: Re: [linux-lvm] Bug report for LVM 1.08
Date: Fri Feb 13 10:03:10 2004	[thread overview]
Message-ID: <20040213150428.GE10943@redhat.com> (raw)
In-Reply-To: <s02bd9d6.050@prv-mail20.provo.novell.com>

Alexander,

the colon output has been added in 1997 to address a SuSE requirement
IRT to easing the installation process and displays the requested fields.

LVM1 is in feature freeze for a long time now in favour
of putting the development focus on LVM2, which is compatible to LVM1.

Please check into the pvs, vgs and lvs commands in LVM2,
which provide formatable output.

Regards,
Heinz    -- The LVM Guy --


On Thu, Feb 12, 2004 at 07:53:44PM -0700, Alexander Danoyan wrote:
> Hello Heinz,
> 
> Here are a few defects.
> There are inconsistency in view between 
> lvdisplay and lvdisplay with -c option
> Here is an example:
> 
> lvdisplay /dev/vg_demo/striped 
> 
> --- Logical volume ---
> LV Name                /dev/vg_demo/striped
> VG Name                vg_demo
> LV Write Access        read/write
> LV Status              available
> LV #                   3
> # open                 0
> LV Size                1 GB
> Current LE             32
> Allocated LE           32
> Stripes                2
> Stripe size (KByte)    4
> Allocation             next free
> Read ahead sectors     1024
> Block device           58:2
> 
> lvdisplay -c /dev/vg_demo/striped 
> /dev/vg_demo/striped:vg_demo:3:1:2:0:2097152:32:32:0:1024:58:2
> 
> 1. As you can see the option -c does not show information about stripes
> at all.
> 2. -c option also does not show information on snapshot volumes
> 
> 3. Also in vgdisplay, pvdisplay and lvdisplay with -c option some of
> the sizes shown in KBytes and some of the sizes in the number of sectors
> ? 
> 
> We are (here at Novell) relying heavily on -c option. 
> Do you have any plans to fix these defects ? 
> If yes when are you planing to have a patch or next release ?
> Thanks a lot.
> 
> Alex.
> 
> _______________________________________________
> linux-lvm mailing list
> linux-lvm@redhat.com
> https://www.redhat.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                                 Red Hat, Inc.
Consulting Development Engineer                   Am Sonnenhang 11
                                                  56242 Marienrachdorf
                                                  Germany
Mauelshagen@RedHat.com                            +49 2626 141200
                                                       FAX 924446
=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-

      reply	other threads:[~2004-02-13 15:04 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-02-13  9:12 [linux-lvm] Bug report for LVM 1.08 Alexander Danoyan
2004-02-13 10:03 ` Heinz 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=20040213150428.GE10943@redhat.com \
    --to=mauelshagen@redhat.com \
    --cc=linux-lvm@redhat.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