From: Andrea Arcangeli <andrea@suse.de>
To: Alan Cox <alan@lxorguk.ukuu.org.uk>
Cc: Mauelshagen@sistina.com, linux-kernel@vger.kernel.org, mge@sistina.com
Subject: Re: LVM 1.0 release decision
Date: Fri, 11 May 2001 17:11:24 +0200 [thread overview]
Message-ID: <20010511171124.M30355@athlon.random> (raw)
In-Reply-To: <20010511162745.B18341@sistina.com> <E14yDyI-0000yE-00@the-village.bc.nu>
In-Reply-To: <E14yDyI-0000yE-00@the-village.bc.nu>; from alan@lxorguk.ukuu.org.uk on Fri, May 11, 2001 at 03:32:46PM +0100
On Fri, May 11, 2001 at 03:32:46PM +0100, Alan Cox wrote:
> Please fix the binary incompatibility in the on disk format between the current
> code and your new release _before_ you do that. The last patches I was sent
> would have screwed every 64bit LVM user.
I just switched to the >=beta4 lvm IOP for all 64bit archs. The previous
one (the 2.4 mainline one) isn't feasible on the archs with 32bit
userspace and 64bit kernel (it uses long). The IOP didn't changed btw,
only the structures changed silenty.
> A new format is fine but import old ones properly. And if you do a new format
It's not a matter of the ondisk format, the on-disk format didn't
changed of course, it's the ioctl format between userspace and kernel
that changed and the userspace only knows about 1 format. Once IOP
changes (or IOP breaks silenty as in this case) you have to upgrade
userspace with the current design.
Andrea
next prev parent reply other threads:[~2001-05-11 15:12 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-05-11 16:27 LVM 1.0 release decision Heinz J. Mauelshagen
2001-05-11 14:32 ` Alan Cox
2001-05-11 15:11 ` Andrea Arcangeli [this message]
2001-05-11 20:12 ` David S. Miller
2001-05-12 1:24 ` Andrea Arcangeli
2001-05-12 1:29 ` David S. Miller
2001-05-12 2:54 ` Andrea Arcangeli
2001-05-12 5:19 ` David S. Miller
2001-05-12 13:39 ` Andrea Arcangeli
2001-05-13 17:36 ` David Woodhouse
2001-05-13 18:39 ` Alan Cox
2001-05-13 23:17 ` Chris Wedgwood
2001-05-13 19:25 ` Christoph Hellwig
2001-05-11 15:42 ` H. Peter Anvin
2001-05-11 17:02 ` Andreas Dilger
2001-05-16 15:03 ` Heinz J. Mauelshagen
2001-05-16 23:38 ` Alan Cox
2001-05-11 14:39 ` Jeff Garzik
2001-05-11 14:48 ` Mark Hahn
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=20010511171124.M30355@athlon.random \
--to=andrea@suse.de \
--cc=Mauelshagen@sistina.com \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=linux-kernel@vger.kernel.org \
--cc=mge@sistina.com \
/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