lvm2 problem - Slackware

This is a discussion on lvm2 problem - Slackware ; I seem to have some troule creating pv's: bash-3.1# fdisk /dev/sda The number of cylinders for this disk is set to 4863. There is nothing wrong with that, but this is larger than 1024, and could in certain setups cause ...

+ Reply to Thread
Results 1 to 6 of 6

Thread: lvm2 problem

  1. lvm2 problem

    I seem to have some troule creating pv's:

    bash-3.1# fdisk /dev/sda

    The number of cylinders for this disk is set to 4863.
    There is nothing wrong with that, but this is larger than 1024,
    and could in certain setups cause problems with:
    1) software that runs at boot time (e.g., old versions of LILO)
    2) booting and partitioning software from other OSs
    (e.g., DOS FDISK, OS/2 FDISK)

    Command (m for help): p

    Disk /dev/sda: 40.0 GB, 40000536576 bytes
    255 heads, 63 sectors/track, 4863 cylinders
    Units = cylinders of 16065 * 512 = 8225280 bytes

    Device Boot Start End Blocks Id System
    /dev/sda1 1 12 96358+ 83 Linux
    /dev/sda2 13 4861 38949592+ 8e Linux LVM

    Command (m for help): q
    bash-3.1# pvcreate -vvv /dev/sda2
    ....
    /dev/vcs6: Not a block device
    /dev/vcs7: Not a block device
    /dev/vcsa: Not a block device
    /dev/vcsa6: Not a block device
    /dev/vcsa7: Not a block device
    /dev/zero: Not a block device
    Wiping internal VG cache
    Locking /var/lock/lvm/P_orphans WB
    /dev/sda2: Skipping (sysfs)
    Device /dev/sda2 not found (or ignored by filtering).
    Unlocking /var/lock/lvm/P_orphans
    bash-3.1# pvscan -vvv
    ....
    /dev/vcsa6: Not a block device
    /dev/vcsa7: Not a block device
    /dev/zero: Not a block device
    Wiping internal VG cache
    Walking through all physical volumes
    /dev/loop0: Skipping (sysfs)
    /dev/sda: Skipping (sysfs)
    /dev/mmcblk0: Skipping (sysfs)
    /dev/loop1: Skipping (sysfs)
    /dev/sda1: Skipping (sysfs)
    /dev/loop2: Skipping (sysfs)
    /dev/sda2: Skipping (sysfs)
    /dev/loop3: Skipping (sysfs)
    /dev/loop4: Skipping (sysfs)
    /dev/loop5: Skipping (sysfs)
    /dev/loop6: Skipping (sysfs)
    /dev/loop7: Skipping (sysfs)
    No matching physical volumes found
    bash-3.1# grep filter /etc/lvm/lvm.conf
    # A filter that tells LVM2 to only use a restricted set of devices.
    # The filter consists of an array of regular expressions. These
    # Don't have more than one filter line active at once: only one
    gets used.
    filter = [ "a/.*/" ]
    # filter = [ "r|/dev/cdrom|" ]
    # filter = [ "a/loop/", "r/.*/" ]
    # filter =[ "a|loop|", "r|/dev/hdc|", "a|/dev/ide|", "r|.*|" ]
    # filter = [ "a|^/dev/hda8$|", "r/.*/" ]
    # The results of the filtering are cached on disk to avoid
    bash-3.1# uname -a
    Linux psion 2.6.24 #56 PREEMPT Tue Jan 29 20:58:40 CET 2008 i686
    Intel(R) Core(TM) Solo CPU U1400 @ 1.20GHz GenuineIntel GNU/Linux
    bash-3.1# vgscan --version
    LVM version: 2.02.09 (2006-08-17)
    Library version: 1.02.19 (2007-04-27)
    Driver version: 4.12.0
    bash-3.1# cat /etc/lvm/.cache
    # This file is automatically maintained by lvm.

    persistent_filter_cache {
    }


    Why this 'Skipping (sysfs)' ?

    --
    Hans

  2. Re: lvm2 problem

    On Thu, 31 Jan 2008 22:44:16 +0100, Hans de Bruin wrote:

    >I seem to have some troule creating pv's:
    ....
    >bash-3.1# uname -a
    >Linux psion 2.6.24 #56 PREEMPT Tue Jan 29 20:58:40 CET 2008 i686
    ....
    >
    >Why this 'Skipping (sysfs)' ?

    Dunno, suggest try 2.6.23.14 since 2.6.24 broke Dell's sysfs, maybe broke
    LVM as well? If it work for 2.6.23.14 please report 2.6.24 regression to
    LKML (kernel.org).

    Grant.
    --
    http://bugsplatter.mine.nu/

  3. Re: lvm2 problem

    On Thu, 31 Jan 2008 22:44:16 +0100, Hans de Bruin wrote:

    > I seem to have some trouble creating pv's:

    PV's are irreproducible and irreplaceable, that is why there is only one
    Slackware.


    :-)

  4. Re: lvm2 problem

    Grant wrote:
    > On Thu, 31 Jan 2008 22:44:16 +0100, Hans de Bruin wrote:
    >
    >> I seem to have some troule creating pv's:
    > ...
    >> bash-3.1# uname -a
    >> Linux psion 2.6.24 #56 PREEMPT Tue Jan 29 20:58:40 CET 2008 i686
    > ...
    >> Why this 'Skipping (sysfs)' ?
    >
    > Dunno, suggest try 2.6.23.14 since 2.6.24 broke Dell's sysfs, maybe broke
    > LVM as well? If it work for 2.6.23.14 please report 2.6.24 regression to
    > LKML (kernel.org).
    >

    Well, I upgraded my via c7 'server' to 6.24 and it still is lvm2
    capable. Now it gets somewhat interesting:

    root@orion:/# pvscan
    OK
    root@orion:/# cd /nfsroot
    root@orion:/# chroot .
    root@orion:/# mount -t proc proc /proc
    root@orion:/# mount -t sys sys /sys
    root@orion:/# pvscan
    Not ok, lots of : Skipping (sysfs)

    Now my laptop is running from /nfsroot. Why, well to delete the
    preinstalled xp partition and create an lvm2 partition on it. The
    nfsroot was already available. I use it to test new kernels on a backup
    c7 board. The kernel config is, except for dhcp & / on nfs, the same as
    on my server. I just added some intel chipset drivers.

    The Dell laptop also had a sort of maintenance fat partiton. It now
    containce a copy of /nfsroot so the laptop can boot from disk. This
    install also suffers from the 'Skipping (sysfs)' mishap

    The nfsroot on the server is just a copy of /

    --
    Hans






  5. Re: lvm2 problem

    Hans de Bruin wrote:
    ....

    c7:

    root@orion:/# ls -l /sys/block/
    total 0
    drwxr-xr-x 5 root root 0 2008-02-01 20:49 dm-0
    drwxr-xr-x 5 root root 0 2008-02-01 20:49 dm-1
    drwxr-xr-x 5 root root 0 2008-02-01 20:49 dm-2
    drwxr-xr-x 5 root root 0 2008-02-01 20:49 dm-3
    drwxr-xr-x 5 root root 0 2008-02-01 20:49 loop0
    drwxr-xr-x 5 root root 0 2008-02-01 20:49 loop1
    drwxr-xr-x 5 root root 0 2008-02-01 20:49 loop2
    drwxr-xr-x 5 root root 0 2008-02-01 20:49 loop3
    drwxr-xr-x 5 root root 0 2008-02-01 20:49 loop4
    drwxr-xr-x 5 root root 0 2008-02-01 20:49 loop5
    drwxr-xr-x 5 root root 0 2008-02-01 20:49 loop6
    drwxr-xr-x 5 root root 0 2008-02-01 20:49 loop7
    drwxr-xr-x 18 root root 0 2008-02-01 20:49 sda
    drwxr-xr-x 6 root root 0 2008-02-01 20:49 sdb
    drwxr-xr-x 6 root root 0 2008-02-01 20:49 sr0
    root@orion:/# cd /nfsroot
    root@orion:/nfsroot# chroot .
    root@orion:/# mount -t sysfs sysfs /sys
    root@orion:/# ls -l /sys/block/
    total 0
    drwxr-xr-x 5 root root 0 2008-02-01 20:53 dm-0
    drwxr-xr-x 5 root root 0 2008-02-01 20:53 dm-1
    drwxr-xr-x 5 root root 0 2008-02-01 20:53 dm-2
    drwxr-xr-x 5 root root 0 2008-02-01 20:53 dm-3
    drwxr-xr-x 5 root root 0 2008-02-01 20:53 loop0
    drwxr-xr-x 5 root root 0 2008-02-01 20:53 loop1
    drwxr-xr-x 5 root root 0 2008-02-01 20:53 loop2
    drwxr-xr-x 5 root root 0 2008-02-01 20:53 loop3
    drwxr-xr-x 5 root root 0 2008-02-01 20:53 loop4
    drwxr-xr-x 5 root root 0 2008-02-01 20:53 loop5
    drwxr-xr-x 5 root root 0 2008-02-01 20:53 loop6
    drwxr-xr-x 5 root root 0 2008-02-01 20:53 loop7
    drwxr-xr-x 18 root root 0 2008-02-01 20:53 sda
    drwxr-xr-x 6 root root 0 2008-02-01 20:53 sdb
    drwxr-xr-x 6 root root 0 2008-02-01 20:53 sr0
    root@orion:/#


    dell laptop:

    bash-3.1# ls -l /sys/block/
    total 0
    lrwxrwxrwx 1 root root 0 2008-02-01 20:48 loop0 ->
    .../devices/virtual/block/loop0
    lrwxrwxrwx 1 root root 0 2008-02-01 20:48 loop1 ->
    .../devices/virtual/block/loop1
    lrwxrwxrwx 1 root root 0 2008-02-01 20:48 loop2 ->
    .../devices/virtual/block/loop2
    lrwxrwxrwx 1 root root 0 2008-02-01 20:48 loop3 ->
    .../devices/virtual/block/loop3
    lrwxrwxrwx 1 root root 0 2008-02-01 20:48 loop4 ->
    .../devices/virtual/block/loop4
    lrwxrwxrwx 1 root root 0 2008-02-01 20:48 loop5 ->
    .../devices/virtual/block/loop5
    lrwxrwxrwx 1 root root 0 2008-02-01 20:48 loop6 ->
    .../devices/virtual/block/loop6
    lrwxrwxrwx 1 root root 0 2008-02-01 20:48 loop7 ->
    .../devices/virtual/block/loop7
    lrwxrwxrwx 1 root root 0 2008-02-01 20:48 mmcblk0 ->
    .../devices/pci0000:00/0000:00:1e.0/0000:02:01.2/mmc_host/mmc0/mmc0:0002/block/mmcblk0
    lrwxrwxrwx 1 root root 0 2008-02-01 20:48 sda ->
    .../devices/pci0000:00/0000:00:1f.1/host0/target0:0:0/0:0:0:0/block/sda
    bash-3.1#

    --
    Hans

  6. Re: lvm2 problem

    Hans de Bruin wrote:
    > I seem to have some troule creating pv's:
    ....

    rm -rf /dev/*

    telinit 6

    pvcreate /dev/sda1

    ok

    pvcreate /dev/mmcblk01

    /dev/mmcblk0p1: Skipping: Unrecognised LVM device type 179

    almost there.

    Maybe copying /dev to a new root of a new disk is something of the past
    and not advisable with udev

    --
    Hans
+ Reply to Thread
« how to sync time for LAN (ntp)? | screen garbage »