From: Andreas Dilger <adilger@turbolinux.com>
To: Linux LVM Development list <lvm-devel@sistina.com>
Cc: Linux kernel development list <linux-kernel@vger.kernel.org>
Subject: Re: LVM 1.0 release decision
Date: Fri, 11 May 2001 11:02:48 -0600 (MDT) [thread overview]
Message-ID: <200105111702.f4BH2mal016240@webber.adilger.int> (raw)
In-Reply-To: <E14yDyI-0000yE-00@the-village.bc.nu> "from Alan Cox at May 11, 2001 03:32:46 pm"
Alan writes (re LVM):
> 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.
>
> A new format is fine but import old ones properly. And if you do a new format
> stop using kdev_t on disk - it will change size soon
Actually, there is no need to store kdev_t on disk at all, nor is there a
need to store device name. By the time you have located the device, you
don't need that information any more. I think that stuff is just a hold
over from when in-core and on-disk data was the same, and should be removed.
Cheers, Andreas
--
Andreas Dilger \ "If a man ate a pound of pasta and a pound of antipasto,
\ would they cancel out, leaving him still hungry?"
http://www-mddsp.enel.ucalgary.ca/People/adilger/ -- Dogbert
next prev parent reply other threads:[~2001-05-11 17:03 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
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 [this message]
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=200105111702.f4BH2mal016240@webber.adilger.int \
--to=adilger@turbolinux.com \
--cc=linux-kernel@vger.kernel.org \
--cc=lvm-devel@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