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

Re: [sarge] Some troubles with LVM2 over RAID1



Just a little tip.
Have edit the lvm.conf?
I had simular troubles but a little etrie in the lvm.conf and it runs.

    # Advanced settings.

    # List of pairs of additional acceptable block device types found
    # in /proc/devices with maximum (non-zero) number of partitions.
    # types = [ "fd", 16 ]
    types = [ "device-mapper", 16 ]
    types = [ "mapper", 16 ]


    # By default, LVM2 will ignore devices used as components of
    # software RAID (md) devices by looking for md superblocks.
    # 1 enables; 0 disables.
    md_component_detection = 1

Check this two opptions.

Ryven

Am Mittwoch 19 April 2006 05:31 schrieb Evgeny Yugov:
> Здравствуйте, debian-sparc.
>
> I have:
> $ uname -a
> Linux bug2 2.4.27-3-sparc64-smp #1 SMP Thu Feb 9 20:32:30 UTC 2006 sparc64
> GNU/Linux
>
> $ dpkg -l *lvm*
> Desired=Unknown/Install/Remove/Purge/Hold
>
> | Status=Not/Installed/Config-files/Unpacked/Failed-config/Half-installed
> |/ Err?=(none)/Hold/Reinst-required/X=both-problems (Status,Err:
> | uppercase=bad)
> |
> ||/ Name                              Version                          
> || Description
>
> +++-=================================-=================================-===
>============================================================================
>=== un  lvm                               <none>                           
> (no description available) un  lvm-binaries                      <none>    
>                        (no description available) ii  lvm-common           
>             1.5.17                            The Logical Volume Manager
> for Linux (common files) pn  lvm10                             <none>      
>                      (no description available) ii  lvm2                   
>           2.01.04-5                         The Linux Logical Volume
> Manager un  lvm5                              <none>                       
>     (no description available) un  lvm6                              <none>
>                            (no description available)
>
> $ sudo mdadm --query --detail /dev/md1
> /dev/md1:
>         Version : 00.90.00
>   Creation Time : Tue Apr 18 10:31:14 2006
>      Raid Level : raid1
>      Array Size : 12566464 (11.98 GiB 12.87 GB)
>     Device Size : 12566464 (11.98 GiB 12.87 GB)
>    Raid Devices : 2
>   Total Devices : 2
> Preferred Minor : 1
>     Persistence : Superblock is persistent
>
>     Update Time : Tue Apr 18 14:52:00 2006
>           State : active
>  Active Devices : 2
> Working Devices : 2
>  Failed Devices : 0
>   Spare Devices : 0
>
>            UUID : e23638bd:e32b6788:08120e29:b0ac17fb
>          Events : 0.5
>
>     Number   Major   Minor   RaidDevice State
>        0       8        4        0      active sync   /dev/sda4
>        1       8       68        1      active sync   /dev/sde4
> But:
> $ sudo mdadm --query /dev/md1
> /dev/md1: 11.98GiB raid1 2 devices, 0 spares. Use mdadm --detail for more
> detail. /dev/md1: No md super block found, not an md component.
> Why?? 8-0
>
> Well, try to create LVM:
> $sudo pvscan
>   PV /dev/md1   VG vgsys   lvm2 [11.98 GB / 11.98 GB free]
>   Total: 1 [11.98 GB] / in use: 1 [11.98 GB] / in no VG: 0 [0   ]
>
> $ sudo vgscan
>   Reading all physical volumes.  This may take a while...
>   Found volume group "vgsys" using metadata type lvm2
>
> $ sudo pvdisplay
>   --- Physical volume ---
>   PV Name               /dev/md1
>   VG Name               vgsys
>   PV Size               11.98 GB / not usable 0
>   Allocatable           yes
>   PE Size (KByte)       4096
>   Total PE              3067
>   Free PE               3067
>   Allocated PE          0
>   PV UUID               E0RwnH-GpiJ-9jyB-3Lo0-FbMG-T7LG-7IhK4N
>
> $ sudo vgdisplay
>   --- Volume group ---
>   VG Name               vgsys
>   System ID
>   Format                lvm2
>   Metadata Areas        1
>   Metadata Sequence No  1
>   VG Access             read/write
>   VG Status             resizable
>   MAX LV                0
>   Cur LV                0
>   Open LV               0
>   Max PV                0
>   Cur PV                1
>   Act PV                1
>   VG Size               11.98 GB
>   PE Size               4.00 MB
>   Total PE              3067
>   Alloc PE / Size       0 / 0
>   Free  PE / Size       3067 / 11.98 GB
>   VG UUID               hVJ3CI-warl-muC5-43lZ-9Cuk-UHCz-hpXeBt
>
> $ sudo lvcreate -n lvusr -L 3G vgsys
>   striped: Required device-mapper target(s) not detected in your kernel
>   lvcreate: Create a logical volume
> ...
> Why "striped"?
> Can i create LVM2 volumes?
>
> $ sudo lsmod
> Module                  Size  Used by    Not tainted
> loop                   10472   3  (autoclean)
> sunhme                 25992   1
> crc32                   3504   0  [sunhme]
> lvm-mod                54384   0  (unused)
> dm-mod                 59336   0
> sr_mod                 16644   0  (unused)
> cdrom                  29184   0  [sr_mod]
> ext3                   92472   2  (autoclean)
> jbd                    47528   2  (autoclean) [ext3]
> sd_mod                 12816  14  (autoclean)
> sym53c8xx_2            78024   7  (autoclean)
> scsi_mod               99232   3  (autoclean) [sr_mod sd_mod sym53c8xx_2]
> raid1                  15496   2  (autoclean)
> md                     55144   3  (autoclean) [raid1]



Reply to: