Re: wrong data unit in lvdiskplay?

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



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


_______________________________________________
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/

[Index of Archives]     [Gluster Users]     [Kernel Development]     [Linux Clusters]     [Device Mapper]     [Security]     [Bugtraq]     [MIPS Linux]     [ARM Linux]     [Linux Security]     [Linux RAID]

  Powered by Linux