Bug 17240

Summary: disturbing message when typing vgs -v, lvs -v, pvs -v, vgdisplay -v ...and so on
Product: Mageia Reporter: peter lawford <petlaw726>
Component: RPM PackagesAssignee: Mageia Bug Squad <bugsquad>
Status: RESOLVED WONTFIX QA Contact:
Severity: minor    
Priority: Low CC: sysadmin-bugs, thierry.vignaud
Version: 5   
Target Milestone: ---   
Hardware: x86_64   
OS: Linux   
Whiteboard:
Source RPM: lvm2-2.02.111-6.mga5 CVE:
Status comment:

Description peter lawford 2015-11-27 19:22:26 CET
Description of problem:
when I run the commands pvs -v, vgs -v, lvs -v, pvdisplay -v, and so on, I get the following disturbing message:
DEGRADED MODE. Incomplete RAID LVs will be processed.
example:

[root@localhost pete]# pvs -v
    DEGRADED MODE. Incomplete RAID LVs will be processed.
    Scanning for physical volume names
  PV         VG        Fmt  Attr PSize   PFree   DevSize PV UUID                               
  /dev/md5   vgmageia  lvm2 a--  120,07g  53,08g 120,07g bODHid-b3vC-TyeM-HI0p-20r5-XOlp-dGYXhD
  /dev/md80  vgstock   lvm2 a--    3,05t   2,19t   3,05t 80auS9-2rWI-0P8E-axWt-GTWq-7GWE-T8tueE
  /dev/md9   vghome    lvm2 a--  885,25g 701,66g 885,25g 6GjPHc-dHwV-bonO-r7A3-HyzT-9a8g-axEgkt
  /dev/sdk1  vgremote  lvm2 a--    2,73t   1,46t   2,73t rtavM4-HC1Q-4Vo0-XQ3h-vh9T-7mub-P6fJYD
  /dev/sdl1  vgremote1 lvm2 a--  931,51g 200,73g 931,51g JHQAog-c0L3-uTHV-dDx4-p61e-u8Th-70ULlk

or

[root@localhost pete]# vgdisplay -v vgstock
    DEGRADED MODE. Incomplete RAID LVs will be processed.
    Using volume group(s) on command line
    Finding volume group "vgstock"
  --- Volume group ---
  VG Name               vgstock
  System ID             
  Format                lvm2
  Metadata Areas        1
  Metadata Sequence No  6
  VG Access             read/write
  VG Status             resizable
  MAX LV                0
  Cur LV                5
  Open LV               0
  Max PV                0
  Cur PV                1
  Act PV                1
  VG Size               3,05 TiB
  PE Size               4,00 MiB
  Total PE              799151
  Alloc PE / Size       225000 / 878,91 GiB
  Free  PE / Size       574151 / 2,19 TiB
  VG UUID               dKs80H-4ceW-9E4k-4nrE-Bnkj-pg96-ukL9dd
   
  --- Logical volume ---
  LV Path                /dev/vgstock/lvstock
  LV Name                lvstock
  VG Name                vgstock
  LV UUID                Efq5wn-7u0p-Tam2-Q7Dp-g0Sh-K5ad-Wuno6W
  LV Write Access        read/write
  LV Creation host, time mageia4_64, 2015-04-24 22:53:27 +0200
  LV Status              available
  # open                 0
  LV Size                195,31 GiB
  Current LE             50000
  Segments               1
  Allocation             inherit
  Read ahead sectors     auto
  - currently set to     8192
  Block device           252:11

.....

Is something wrong or is it only an annoying message? without the "-v" option, everything OK; example: 

[root@localhost pete]# vgs
  VG        #PV #LV #SN Attr   VSize   VFree  
  vghome      1   5   0 wz--n- 885,25g 701,66g
  vgmageia    1  12   0 wz--n- 120,07g  53,08g
  vgremote    1   4   0 wz--n-   2,73t   1,46t
  vgremote1   1   4   0 wz--n- 931,51g 200,73g
  vgstock     1   5   0 wz--n-   3,05t   2,19t 

and the same for the others lvm2 commands.

I have checked all my vg's, lv's and pv's, eveything OK

cat /proc/mdstat returns:

[root@localhost pete]# cat /proc/mdstat 
Personalities : [raid0] [raid6] [raid5] [raid4] 
md5 : active raid5 sdc5[2] sdb5[1] sdd5[3] sda5[0]
      125906112 blocks level 5, 64k chunk, algorithm 2 [4/4] [UUUU]
      
md9 : active raid5 sdc9[2] sdb9[1] sdd9[3] sda9[0]
      928256256 blocks level 5, 128k chunk, algorithm 2 [4/4] [UUUU]
      
md80 : active raid6 sde8[0] sdf8[1] sdj8[5] sdi8[4] sdh8[3] sdg8[2]
      3273324544 blocks super 1.2 level 6, 512k chunk, algorithm 2 [6/6] [UUUUUU]
      bitmap: 0/7 pages [0KB], 65536KB chunk

md30 : active raid0 sdf3[1] sde3[0] sdj3[5] sdi3[4] sdg3[2] sdh3[3]
      6264960 blocks 64k chunks



Version-Release number of selected component (if applicable):


How reproducible:run these commands with and without -v option


Steps to Reproduce:see above
1.
2.
3.


Reproducible: 

Steps to Reproduce:
Comment 1 Thierry Vignaud 2015-11-30 13:15:25 CET
Why do you use the -v option?
You're being misleaded by it
(You don't have any mirrored volumes)

Priority: Normal => Low
Status: NEW => RESOLVED
CC: (none) => thierry.vignaud
Component: Release (media or process) => RPM Packages
Resolution: (none) => WONTFIX
Severity: normal => minor

Comment 2 peter lawford 2015-11-30 21:26:44 CET
(In reply to Thierry Vignaud from comment #1)
> Why do you use the -v option?
> You're being misleaded by it
> (You don't have any mirrored volumes)

I use -v option to know more about my LVM config; as an example:

[root@localhost pete]# vgdisplay vghome
  --- Volume group ---
  VG Name               vghome
  System ID             
  Format                lvm2
  Metadata Areas        1
  Metadata Sequence No  80
  VG Access             read/write
  VG Status             resizable
  MAX LV                0
  Cur LV                4
  Open LV               3
  Max PV                0
  Cur PV                1
  Act PV                1
  VG Size               885,25 GiB
  PE Size               4,00 MiB
  Total PE              226624
  Alloc PE / Size       43000 / 167,97 GiB
  Free  PE / Size       183624 / 717,28 GiB
  VG UUID               ND0J2v-3dSh-mLWO-hJbt-LsSz-sQwO-V5u71o

[root@localhost pete]# vgdisplay -v vghome
    DEGRADED MODE. Incomplete RAID LVs will be processed.
    Using volume group(s) on command line
    Finding volume group "vghome"
  --- Volume group ---
  VG Name               vghome
  System ID             
  Format                lvm2
  Metadata Areas        1
  Metadata Sequence No  80
  VG Access             read/write
  VG Status             resizable
  MAX LV                0
  Cur LV                4
  Open LV               3
  Max PV                0
  Cur PV                1
  Act PV                1
  VG Size               885,25 GiB
  PE Size               4,00 MiB
  Total PE              226624
  Alloc PE / Size       43000 / 167,97 GiB
  Free  PE / Size       183624 / 717,28 GiB
  VG UUID               ND0J2v-3dSh-mLWO-hJbt-LsSz-sQwO-V5u71o
   
  --- Logical volume ---
  LV Path                /dev/vghome/lvhomedoc
  LV Name                lvhomedoc
  VG Name                vghome
  LV UUID                aPSs7w-Nj55-pSXs-ac3f-AvE7-5hZ6-c116VS
  LV Write Access        read/write
  LV Creation host, time , 
  LV Status              available
  # open                 1
  LV Size                117,19 GiB
  Current LE             30000
  Segments               1
  Allocation             inherit
  Read ahead sectors     auto
  - currently set to     1536
  Block device           252:16
   
  --- Logical volume ---
  LV Path                /dev/vghome/lvscratch
  LV Name                lvscratch
  VG Name                vghome
  LV UUID                6AdU7A-caJP-HYY1-26LL-W47y-zO6m-6pH3sF
  LV Write Access        read/write
  LV Creation host, time , 
  LV Status              available
  # open                 1
  LV Size                19,53 GiB
  Current LE             5000
  Segments               1
  Allocation             inherit
  Read ahead sectors     auto
  - currently set to     1536
  Block device           252:17
   
  --- Logical volume ---
  LV Path                /dev/vghome/lvhomemga4-64
  LV Name                lvhomemga4-64
  VG Name                vghome
  LV UUID                z9ypWA-l4UZ-uDvF-4sPj-2KSB-nCD5-Aw5CiL
  LV Write Access        read/write
  LV Creation host, time mageia3_64, 2014-02-06 14:03:02 +0100
  LV Status              available
  # open                 0
  LV Size                15,62 GiB
  Current LE             4000
  Segments               1
  Allocation             inherit
  Read ahead sectors     auto
  - currently set to     1536
  Block device           252:18
   
  --- Logical volume ---
  LV Path                /dev/vghome/lvhomemga5-64
  LV Name                lvhomemga5-64
  VG Name                vghome
  LV UUID                y1i2CI-sRJO-GMGn-zVsq-kSIy-gf0U-v7zwhN
  LV Write Access        read/write
  LV Creation host, time mageia4_64, 2015-06-21 01:11:04 +0200
  LV Status              available
  # open                 1
  LV Size                15,62 GiB
  Current LE             4000
  Segments               1
  Allocation             inherit
  Read ahead sectors     auto
  - currently set to     1536
  Block device           252:19
   
  --- Physical volumes ---
  PV Name               /dev/md9     
  PV UUID               6GjPHc-dHwV-bonO-r7A3-HyzT-9a8g-axEgkt
  PV Status             allocatable
  Total PE / Free PE    226624 / 183624

in this example, with -v option, I have datas about logical volumes in the vg I have not without -v option

but what is the sense of the message:
DEGRADED MODE. Incomplete RAID LVs will be processed.
    Using volume group(s) on command line
and its relationship with mirror volumes?