Re: [linux-lvm] LVs with the same LV#.

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

 



Terje Kvernes <terjekv@math.uio.no> writes:

>   a 'vgdisplay -v' ends with the following:
> 
> --- Logical volume ---
> LV Name                /dev/cornucopia/gjester-u1
> VG Name                cornucopia
> LV Write Access        read/write
> LV Status              available
> LV #                   7
> # open                 0
> LV Size                2.00 GB
> Current LE             32
> Allocated LE           32
> Allocation             next free
> Read ahead sectors     10000
> Block device           58:6
> 
> --- Logical volume ---
> LV Name                /dev/cornucopia/ansatte-u1
> VG Name                cornucopia
> LV Write Access        read/write
> LV Status              available
> LV #                   7
> # open                 0
> LV Size                2.00 GB
> Current LE             256
> Allocated LE           256
> Allocation             next free
> Read ahead sectors     10000
> Block device           58:6

  for the record, when we finally booted the box everything was fine,
  both LV's where gone.  umount and a couple of vgchanges probably
  would have solved the issue.  :)

-- 
Terje

_______________________________________________
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

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

  Powered by Linux