lkml.org 
[lkml]   [2004]   [Jan]   [7]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
 
Messages in this thread
    /
    Date
    From
    SubjectRe: LVM 2.6 compatibility?
    On Wed, 2004-01-07 09:41:17 +0100, venom@sns.it <venom@sns.it>
    wrote in message <Pine.LNX.4.43.0401070941040.23681-100000@cibs9.sns.it>:
    >
    > yes, there is full back compatibility

    Erm, not to mention that I've recently been hit by some bug. This is
    with LVM2 userland and LVM1 metadata. I just wanted to create a
    snapshot, but I got

    machineA#
    Rounding up size to full physical extend 252.00 MB
    device-mapper: error adding target to table
    device-mapper ioctl cmd 9 failed: Invalid argument
    Couldn't load device 'vg00-snap1'.
    Problem reactivating origin home_lv

    and

    which leaves me with:

    machineB:~# lvdisplay
    --- Logical volume ---
    LV Name /dev/storage_vg/whole_ftp_area_lv
    VG Name storage_vg
    LV UUID 000000-0000-0000-0000-0000-0000-000000
    LV Write Access read/write
    LV snapshot status source of
    /dev/storage_vg/tempsnap [INACTIVE]
    LV Status NOT available
    LV Size 182.50 GB
    Current LE 2920
    Segments 23
    Allocation next free
    Read ahead sectors 0

    --- Logical volume ---
    LV Name /dev/storage_vg/public_storage_lv
    VG Name storage_vg
    LV UUID 000000-0000-0000-0000-0000-0000-000001
    LV Write Access read/write
    LV Status available
    # open 1
    LV Size 54.38 GB
    Current LE 870
    Segments 8
    Allocation next free
    Read ahead sectors 0
    Block device 254:3

    --- Logical volume ---
    LV Name /dev/storage_vg/tempsnap
    VG Name storage_vg
    LV UUID 000000-0000-0000-0000-0000-0000-000002
    LV Write Access read/write
    LV snapshot status INACTIVE destination for /dev/storage_vg/whole_ftp_area_lv
    LV Status available
    # open 0
    LV Size 182.50 GB
    Current LE 2920
    Segments 1
    Snapshot chunk size 8.00 KB
    Allocated to snapshot 100.00%
    Allocation next free
    Read ahead sectors 0
    Block device 254:2

    So, after lvcreate -s on two different hosts, the snapshot isn't really
    there (albeit vgmknodes creates nodes for them), but any attempt to
    access them results in "they're not there". Worse than that, if the
    original LV was mounted, anything accessing it will hang in D state, of
    course:)

    MfG, JBG

    --
    Jan-Benedict Glaw jbglaw@lug-owl.de . +49-172-7608481
    "Eine Freie Meinung in einem Freien Kopf | Gegen Zensur | Gegen Krieg
    fuer einen Freien Staat voll Freier Bürger" | im Internet! | im Irak!
    ret = do_actions((curr | FREE_SPEECH) & ~(NEW_COPYRIGHT_LAW | DRM | TCPA));
    [unhandled content-type:application/pgp-signature]
    \
     
     \ /
      Last update: 2005-03-22 13:59    [W:0.023 / U:0.404 seconds]
    ©2003-2016 Jasper Spaans. hosted at Digital OceanAdvertise on this site