LVM 2.6 compatibility?

LVM 2.6 compatibility?

[Roy Sigurd Karlsbakk]

hi all

I have this archive server running 2.4 and LVM across two 3ware hardware
RAID-5 sets with 8 drives each. Now, upgrading the server, I want a new
logical volume >2TB so I need 2.6. But - one of the logical volumes
would be very nice to keep. Can I upgrade to 2.6 and keep the old LV?

roy

Re: LVM 2.6 compatibility?

[Måns Rullgård]

Roy Sigurd Karlsbakk <roy@karlsbakk.net> writes:

> hi all
>
> I have this archive server running 2.4 and LVM across two 3ware hardware
> RAID-5 sets with 8 drives each. Now, upgrading the server, I want a new
> logical volume >2TB so I need 2.6. But - one of the logical volumes
> would be very nice to keep. Can I upgrade to 2.6 and keep the old LV?

Yes.  LVM2 understands the LVM1 metadata format.

-- 
Måns Rullgård
mru@kth.se

Re: LVM 2.6 compatibility?

[venom]

yes, there is full back compatibility

On Tue, 6 Jan 2004, Roy Sigurd Karlsbakk wrote:

> Date: Tue, 06 Jan 2004 14:59:28 +0100
> From: Roy Sigurd Karlsbakk <roy@karlsbakk.net>
> To: Linux Kernel Mailinglist <linux-kernel@vger.kernel.org>
> Subject: LVM 2.6 compatibility?
>
> hi all
>
> I have this archive server running 2.4 and LVM across two 3ware hardware
> RAID-5 sets with 8 drives each. Now, upgrading the server, I want a new
> logical volume >2TB so I need 2.6. But - one of the logical volumes
> would be very nice to keep. Can I upgrade to 2.6 and keep the old LV?
>
> roy
>
> -
> To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at  http://vger.kernel.org/majordomo-info.html
> Please read the FAQ at  http://www.tux.org/lkml/
>

Re: LVM 2.6 compatibility?

[Jan-Benedict Glaw]

[-- Attachment #1: Type: text/plain, Size: 3076 bytes --]

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));

[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 189 bytes --]

Re: LVM 2.6 compatibility?

[Christophe Saout]

Am Mi, den 07.01.2004 schrieb Jan-Benedict Glaw um 10:09:

> 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

Snapshots are not yet finished. There is experimental support in the
unstable device-mapper development tree. There's also experimental
support for pvmove there, and some new dm targets (multipath and crypt).