[Date Prev][Date Next]   [Thread Prev][Thread Next]   [Thread Index] [Date Index] [Author Index]

[linux-lvm] Re: *** ANNOUNCEMENT *** LVM 1.0 available at www.sistina.com

Hi Heinz,

thanks for your answer!

On Fri, Aug 17, 2001 at 11:16:36AM +0200, Heinz J . Mauelshagen wrote:
> I just picked your e-mail standing for a couple to summarize:
> - some people report, that the bi-directional upgrade path from
>   <= LVM 0.9.1 Beta 7 to LVM 0.9.1 Beta 8 and beyond is fine

For individuals that are doing their installations manually, the approach
offered by you is no serious obstacle, I think.

The problem is those relying on the distributor to handle such things and
those are the vast majority of people. And, indeed, it's the distributor's
job to handle the complexity involved in things as LVM.

Now, we have to offer a fail proof upgrade from all our deployed LVM
versions for the customers. If we can't do it, we can't do the update,
because customers just won't accept it.

Ideally, we would not need to worry, as new lvm utils and the new lvm code
in kernel would handle old formats as well. 
For an important piece of software that is used by a large user base, that
would be an absolute requirement.

Now, I know that the world is not ideal, and people make mistakes.

Look at Berkeley db and guess why people more and more refrain from using it.
reiserfs had a similar problems with on-disk format changes in the past and
we really had to work hard with the reiser people to get it fixed. But it
happened and we could continue recommending reiserfs, as it could be used
without major pains.

I'm very unhappy to see that LVM has similar problems. On disk format
changes should normally not be required, as you should use an extendable
format that does only get new, added fields, which aren't required by old
versions. New versions would either fill them in automatically or be able to
do without them, at least for a few revisions.

To give an example: reiserfs 3.6.x code (in kernel 2.4) can read and write
the 3.5 on-disk format (in 2.2 SuSE kernels) without problems, so you can go
forward and backward between 2.2 and 2.4 kernels without problems.
If you need the new 3.6 features, you can convert by simply using a
mount parameter and only then there's no way back.
This is an ideal way of dealing with updating file/on-disk formats.

I hope you agree that this would be the desirable way to go.

People need to be confident that using a technology, such as reiser (or
LVM), does not give them headaches in the future, because they can't
upgrade any more.

So far for our concerns. I hope they are very clear now.

Now, for some reasons, things are not so ideal.
So we need to try to keep the damage as small as possible.

> - some people complain that there could be an easier solution
>   and that there are just 2 cases to distinguish which could easily be covered
>   by a better upgrade tool which is *not* true
> As Joe stated easily and I tried to explain briefly a while ago:
> there's multiple cases and the solution we have right now seemed to be the
> cleanest approach to cover them all *without* hitting the trape of missing 
> some!

Did I correctly understand him that there's no straight-forward way to
determine the LVM on-disk version? Hard to believe ...
You know what the next field to be added should be IMHO then, I guess?
(In all of the file formats I've been designing recently, I put a magic
 number to recognize the format plus a version number right at the

Now, we (SuSE) were using beta versions of LVM, as we wanted to push LVM
development and testing on the one hand and wanted to provide the features
for our users on the other hand.
I would have assumed that this has been discussed with you before?
If not, it was not such a good idea to use the beta versions.
Maybe things also went wrong there :-(
Hopefully this can be improved for the future then.

> Because we take your complaints seriously we are investigating, if there's a
> well defined finite amount of cases that we actually can cover with a simple
> tool. 

As far as I can see, there's 0.8, 0.9, 0.9.1b4 and 0.9.1b7 in widespread use
out in the wild.
Ideally, we could handle all of them easily. Less ideally, only a subset of
them ...

> If so, you are going get it ;-)
> Please stay tuned and give as some time...

Now, this sound very good. I'd be very happy if we find a solution which
lets those people not alone that used older LVM versions relying on the
distribution support.

I would offer you help with working on it, but as I personally do not have
resources to do programming on LVM tools, I can't promise anything. But I'm
optimistic some colleagues will also want to help if necessary.
What we can and will do is testing.

> We'll keep you posted.
> Thanks for your understanding!

Thanks for addressing our concerns!

Kurt Garloff                   <kurt garloff de>         [Eindhoven, NL]
Physics: Plasma simulations  <K Garloff Phys TUE NL>  [TU Eindhoven, NL]
Linux: SCSI, Security          <garloff suse de>    [SuSE Nuernberg, DE]
 (See mail header or public key servers for PGP2 and GPG public keys.)

Attachment: pgp00017.pgp
Description: PGP signature

[Date Prev][Date Next]   [Thread Prev][Thread Next]   [Thread Index] [Date Index] [Author Index]