All of lore.kernel.org
 help / color / mirror / Atom feed
From: James <superfueld@charter.net>
To: mingz@ele.uri.edu,
	LVM general discussion and development <linux-lvm@redhat.com>
Subject: Re: [linux-lvm] wrong data unit in lvdiskplay?
Date: Wed, 14 Jul 2004 14:43:27 -0500	[thread overview]
Message-ID: <40F58CDF.3010100@charter.net> (raw)
In-Reply-To: <1089746889.2988.20.camel@Smeagol.geministorage.com>

I don't think this is your error. I'm seeing th same output on my systems and I don't like it. Thanks for pointing this out before I wrote some script to parse the INCORRECT output of lvdisplay -c.

FYI: I checked the redhat bugzilla and couldn't find a mention of this, so I entered this as bug #127858.

Ming Zhang wrote:
> I am not sure if this is a bug or my stupid error.
> 
> I am using lvm-1.0.3-13, which come from Fedora core 1. I created a
> lvol1 with size -L 2000M. then
> 
> # lvdisplay /dev/vg1/lvol1
> --- Logical volume ---
> LV Name                /dev/vg1/lvol1
> VG Name                vg1
> LV Write Access        read/write
> LV Status              available
> LV #                   1
> # open                 0
> LV Size                1.95 GB
> Current LE             500
> Allocated LE           500
> Allocation             next free
> Read ahead sectors     1024
> Block device           58:0
> 
> # lvdisplay -c /dev/vg1/lvol1
> /dev/vg1/lvol1:vg1:3:1:0:0:4096000:500:500:0:1024:58:0
>                                                                                            here i found that its size is 4096000. base on the document of lvdiskplay, this should be in KB unit. so two output from lvdisplay is mismatched. can anybody tell me why?
> 
> 
> 
> ming
> 
> 

      reply	other threads:[~2004-07-14 19:44 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-07-13 19:28 [linux-lvm] wrong data unit in lvdiskplay? Ming Zhang
2004-07-14 19:43 ` James [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=40F58CDF.3010100@charter.net \
    --to=superfueld@charter.net \
    --cc=linux-lvm@redhat.com \
    --cc=mingz@ele.uri.edu \
    /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.