]>
Commit | Line | Data |
---|---|---|
25579907 AK |
1 | Version 2.00.16 - |
2 | ============================= | |
3 | Support for tagged config files. | |
4 | Don't abort operations if selinux present but disabled. | |
5 | Fix typo in configure which left HAVE_LIBDL unset. | |
6 | ||
a38df97f AK |
7 | Version 2.00.15 - 19 Apr 2004 |
8 | ============================= | |
9 | configure --with-owner= --with-group= to avoid -o and -g args to 'install' | |
10 | ||
96185e9c AK |
11 | Version 2.00.14 - 16 Apr 2004 |
12 | ============================= | |
13 | Use 64-bit file functions by default. | |
14 | ||
01c6121b | 15 | Version 2.00.13 - 16 Apr 2004 |
121c5c06 | 16 | ============================= |
01c6121b AK |
17 | Set devices/md_component_detection = 1 to ignore devices containing md |
18 | superblocks. [Luca Berra] | |
121c5c06 AK |
19 | Ignore error setting selinux file context if fs doesn't support it. |
20 | ||
a218a29c AK |
21 | Version 2.00.12 - 14 Apr 2004 |
22 | ============================= | |
4563e036 AK |
23 | Install a default lvm.conf into /etc/lvm if there isn't one already. |
24 | Allow different installation dir for lvm.static (configure --staticdir=) | |
25 | Fix inverted selinux error check. | |
26 | Recognise power2 in /proc/devices. | |
27 | Fix counting in lvs_in_vg_opened. [It ignored devices open more than once.] | |
28 | ||
e5b28125 AK |
29 | Version 2.00.11 - 8 Apr 2004 |
30 | ============================ | |
31 | Set fallback_to_lvm1 in lvm.conf (or configure --enable-lvm1_fallback) | |
32 | to run lvm1 binaries if running a 2.4 kernel without device-mapper. | |
33 | ||
0d0b3357 | 34 | Version 2.00.10 - 7 Apr 2004 |
35030bb0 AK |
35 | ============================ |
36 | More fixes for static build. | |
0d0b3357 AK |
37 | Add basic selinux support. |
38 | Fix sysfs detection. | |
35030bb0 | 39 | |
6b493d07 AK |
40 | Version 2.00.09 - 31 Mar 2004 |
41 | ============================= | |
cd242223 AK |
42 | Update copyright notices for Red Hat. |
43 | Fix vgmknodes to remove dud /dev/mapper entries. (libdevmapper update reqd). | |
44 | Add LVM1-style colon output to vgdisplay. | |
45 | lvchange --refresh to reload active LVs. | |
46 | Add string display to memory leak dump. | |
47 | Add locking flags & memlock option. | |
48 | Add list_versions to library. | |
49 | Ignore open hidden LVs when checking if deactivation is OK. | |
50 | Suppress move percentage when device inactive. | |
51 | Add lv_info_by_lvid. | |
52 | Various tidy-ups to the build process. | |
53 | Rebaseline internal verbose level. | |
54 | Add --nolocking option for read operations if locking is failing. | |
55 | Add option to compile into a library. | |
56 | When compiled without libdevmapper, only print warning message once. | |
57 | Fix lvreduce PV extent calculations. | |
58 | Fix DESTDIR to work with configure path overrides. | |
59 | Always use / as config file separator & rename internal config file variables. | |
60 | Add support for tagging PV/VG/LVs and hosts. | |
61 | Fix rare bug in recognition of long cmdline argument forms. | |
62 | Add basic internationalisation infrastructure. | |
63 | Don't recurse symlinked dirs such as /dev/fd on 2.6 kernels. | |
64 | Update autoconf files. | |
65 | Add sysfs block device filtering for 2.6 kernels. | |
66 | Update refs for move to sources.redhat.com. | |
67 | ||
f74d51d9 AK |
68 | Friday 14th November 2003 |
69 | ========================= | |
70 | Some bug fixes & minor enhancements, including: | |
71 | Backwards compatibility with LVM1 metadata improved. | |
72 | Missing man pages written. | |
73 | Tool error codes made more consistent. | |
74 | vgmknodes written. | |
75 | O_DIRECT can be turned off if it doesn't work in your kernel. | |
b2bb7264 | 76 | dumpconfig to display the active configuration file |
f74d51d9 AK |
77 | |
78 | You need to update libdevmapper before using 'vgmknodes' or 'vgscan --mknodes'. | |
79 | If your root filesystem is on an LV, you should run one of those two | |
80 | commands to fix up the special files in /dev in your real root filesystem | |
81 | after finishing with your initrd. Also, remember you can use | |
82 | 'vgchange --ignorelockingfailure' on your initrd if the tool fails because | |
83 | it can't write a lock file to a read-only filesystem. | |
84 | ||
541f8753 AK |
85 | Wednesday 30th April 2003 |
86 | ========================= | |
87 | A pvmove implementation is now available for the new metadata format. | |
88 | ||
89 | When running a command that allocates space (e.g. lvcreate), you can now | |
90 | restrict not only which disk(s) may be used but also the Physical Extents | |
91 | on those disks. e.g. lvcreate -L 10 vg1 /dev/hda6:1000-2000:3000-4000 | |
92 | ||
93 | ||
94 | Monday 18th November 2002 | |
5a52dca9 AK |
95 | ======================== |
96 | ||
97 | The new format of LVM metadata is ready for you to test! | |
98 | We expect it to be more efficient and more robust than the original format. | |
99 | It's more compact and supports transactional changes and replication. | |
100 | Should things go wrong on a system, it's human-readable (and editable). | |
101 | ||
102 | Please report any problems you find to the mailing list, | |
103 | linux-lvm@sistina.com. The software has NOT yet been thoroughly | |
104 | tested and so quite possibly there'll still be some bugs in it. | |
105 | Be aware of the disclaimer in the COPYING file. | |
106 | ||
107 | While testing, we recommend turning logging on in the configuration file | |
108 | to provide us with diagnostic information: | |
109 | log { | |
110 | file="/tmp/lvm2.log" | |
541f8753 | 111 | level=7 |
5518374b | 112 | activation=1 |
5a52dca9 AK |
113 | } |
114 | ||
115 | You should schedule regular backups of your configuration file and | |
116 | metadata backups and archives (normally kept under /etc/lvm). | |
117 | ||
118 | Please read docs/example.conf and "man lvm.conf" to find out more about | |
119 | the configuration file. | |
120 | ||
121 | To convert an existing volume group called vg1 to the new format using | |
122 | the default settings, use "vgconvert -M2 vg1". See "man vgconvert". | |
123 | ||
124 | -M (or --metadatatype in its long form) is a new flag to indicate which | |
125 | format of metadata the command should use for anything it creates. | |
126 | Currently, the valid types are "lvm1" and "lvm2" and they can be | |
127 | abbreviated to "1" and "2" respectively. The default value for this | |
128 | flag can be changed in the global section in the config file. | |
129 | ||
130 | Backwards-compatible support for the original LVM1 metadata format is | |
131 | maintained, but it can be moved into a shared library or removed | |
132 | completely with configure's --with-lvm1 option. | |
133 | ||
134 | Under LVM2, the basic unit of metadata is the volume group. Different | |
135 | volume groups can use different formats of metadata - vg1 could use | |
136 | the original LVM1 format while vg2 used the new format - but you can't | |
137 | mix formats within a volume group. So to add a PV to an LVM2-format | |
138 | volume group you must run "pvcreate -M2" on it, followed by "vgextend". | |
139 | ||
140 | With LVM2-format metadata, lvextend will let you specify striping | |
141 | parameters. So an LV could consist of two or more "segments" - the | |
142 | first segment could have 3 stripes while the second segment has just 2. | |
143 | ||
144 | LVM2 maintains a backup of the current metadata for each volume group | |
145 | in /etc/lvm/backup, and puts copies of previous versions in | |
146 | /etc/lvm/archive. "vgcfgbackup" and "vgcfgrestore" can be used to | |
147 | create and restore from these files. If you fully understand what | |
148 | you're doing, metadata can be changed by editing a copy of a current | |
149 | backup file and using vgcfgrestore to reload it. | |
150 | ||
151 | Please read the pvcreate man page for more information on the new | |
152 | format for metadata. | |
153 | ||
154 | All tools that can change things have a --test flag which can be used | |
155 | to check the effect of a set of cmdline args without really making the | |
156 | changes. | |
157 | ||
158 | ||
159 | What's not finished? | |
160 | ==================== | |
161 | The internal cache. If you turn on debugging output you'll see lots of | |
914c9723 | 162 | repeated messages, many of which will eventually get optimised out. |
5a52dca9 AK |
163 | |
164 | --test sometimes causes a command to fail (e.g. vgconvert --test) even | |
165 | though the real command would work: again, fixing this is waiting for | |
166 | the work on the cache. | |
167 | ||
168 | Several of the tools do not yet contain the logic to handle full | |
169 | recovery: combinations of pvcreate and vgcfgrestore may sometimes be | |
170 | needed to restore metadata if a tool gets interrupted or crashes or | |
171 | finds something unexpected. This applies particularly to tools that | |
172 | work on more than one volume group at once (e.g. vgsplit). | |
173 | ||
174 | Display output. Some metadata information cannot yet be displayed. | |
5a52dca9 AK |
175 | |
176 | Recovery tools to salvage "lost" metadata directly from the disks: | |
177 | but we hope the new format will mean such tools are hardly ever needed! | |
178 |