public inbox for gentoo-dev@lists.gentoo.org
 help / color / mirror / Atom feed
From: Thilo Bangert <thilo.bangert@gmx.net>
To: gentoo-dev@gentoo.org
Subject: Re: [gentoo-dev] LVM and ataraid
Date: Sat, 2 Mar 2002 13:25:38 +0100	[thread overview]
Message-ID: <20020302123842.C122B2015DAE@chiba.3jane.net> (raw)
In-Reply-To: <20020228221044.B7E592015D90@chiba.3jane.net>

Hi,

the patches from lvm 1.0.3 applied nicely to the 2.4.18, compiling 
went fine too, now i just need to use it..

i sure like to see this in the (gentoo||vanilla) kernel some time
greetings
Thilo


On Thursday, 28. February 2002 23:07, you wrote:
> Hi,
>
> today i tried to setup a LVM on a ataraid device. This failed
> because, LVM-1.0.1-rc4 does not support ataraid devices. i atteched
> a new lvm-user ebuild which updates LVM to 1.0.3 (which includes
> support for ataraid devices)... it's basically a copy+paste of the
> old one.
> it compiled nicely on my homemachine - and i will use it with the
> gentoo bootdisc tommorrow...
>
> this is bug #898
>
> thanks
> Thilo
>
> >from LVM's changelog:
>
> ===
> 						27/05/1998 -
> 						$Date: 2002/02/18 17:49:01 $
>
> Logical Volume Manager Changelog
>
> Changelog for 1.0.2 to 1.0.3
>
> LVM
> ---
>
> Tool fixes to support physical and logical volumes bigger than 1
> Terabyte
> and up to 2 Terabytes in size.
>
>
> Driver
> ------
>
>
> Tools
> -----
>
> o lvcreate
> o lvextend
> o lvreduce
>  - support logical volume sizes up to 2TB - 1 sector
>
> o pvcreate
>   - option -s to overwrite the device size. Useful to fake physical
>     volumes on smaller devices for test purposes or to set the
> device size
>     correctly in case the OS reports a wrong one in rare cases
>
> o pvmove (involves pv_move_pes() in the library as well)
>   - supports moves in inactive volume groups now
>   - new option "-i" to ignore read errors on flaky or otherwise
>     inaccessible devices
>
> o vgcfgrestore
>   - option -b to give a backup history number together with "-n
> VolumeGroupName"
>   - option -i to ignore the size of the device to be restored to
>   - no need to give -n *and* -f any longer
>
> o vgcreate: remove wrong check for ~64k extents maximum
>
> o vgchange
>   - drop snapshot logical volumes which have broken exception
> tables during volume group activation
>
> o vgexport can now export volume groups which are not in
> /etc/lvmtab*
>
> o vgscan
>   - option -f to force changes of volume group and logical volume
> device numbers
>     which potentially violates NFS client access in case of
> exported filesystems
>     on changed logical volumes
>   - option -r to remove all snapshots in all volume groups or
> snapshots in
>     a specified volume group (useful in case snapshots are corrupt)
>
>
> Library
> -------
>
> o lvm_check_number_ll
>   - new (long long) returning function to convert
>     number strings with optional size suffixes
>
> o lvm_tab_check_free_lv_number
>   - new function to check if a single logical volume device number
>     is already used
>
> o pv_get_size_ll
>   - new ( long long) returning function to support 1TB < PV size <
> 2TB
>
> o pv_move_pes
>   - support for moves in inactive volume groups and for ignoring
> read errors
>
> o pv_write
>   - zero gap between PV structure and VG structure on disk in order
>     to avoid confusing other tools
>
>
>
> ===================================================================
>============
>
> Changelog for 1.0.1 to 1.0.2
>
> LVM
> ---
>
> Driver
> ------
>
> o now works with 2.4.17
>
> o reduce stack footprint with snapshots
>
> o sparc 64 fixes (tests needed!)
>
> o avoid oops when accessing PVs of an inactive VG
>
> Tools
> -----
>
> o persistent LV device minors to support client recovery after
>   a NFS server reboot/failover
>
> o ataraid device support
>
> o support loop devices (they do not show up in /proc/partitions)
>
> o fixed contiguous PV array bug in pv_read_all_pv_of_vg.c
>
> o avoid flushing PVs
>
> o DAC960 recognition bugs fixed
>
> ===================================================================
>============
>
> Changelog for 1.0 to 1.0.1
>
> LVM
> ---
>
> LVM now supports both version 1 and version 2 data formats.  No
> need to
> upgrade !
>
> Driver
> ------
>
> o now works with 2.4.16
>
> Tools
> -----
>
> o support for version 1 and 2 data formats
>
> o Now stores new and changed PVs in version 1 data format!
>
> o zero pv and lv arrays in vg_cfgrestore
>
> o removing of PVs from VGs with snapshot now works
>   (changes in pv_read_all_pv_of_vg(), pv_read_all_pe_of_vg(),
>    vg_setup_for_merge(), vg_setup_for_extend(),
> vg_setup_for_reduce(), vg_setup_for_split() and liblvm.h)
>
> o persistant LV and PV numbers
>
> o lvmcreate_initd now supports devfs
>
> o support for non-partitioned MDs
>
> o SPARC compilation fixes
>
> ===================================================================
>============


  reply	other threads:[~2002-03-02 12:38 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-02-28 22:07 [gentoo-dev] LVM and ataraid Thilo Bangert
2002-03-02 12:25 ` Thilo Bangert [this message]
2002-03-04 11:02   ` Thilo Bangert

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20020302123842.C122B2015DAE@chiba.3jane.net \
    --to=thilo.bangert@gmx.net \
    --cc=gentoo-dev@gentoo.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox