From: "Stephen C. Tweedie" <sct@redhat.com>
To: Andreas Dilger <adilger@enel.ucalgary.ca>
Cc: Linux LVM mailing list <linux-lvm@msede.com>,
Linux FS development list <linux-fsdevel@vger.rutgers.edu>,
Stephen Tweedie <sct@redhat.com>
Subject: Re: [linux-lvm] Re: ext2resize
Date: Mon, 5 Jul 1999 18:03:02 +0100 (BST) [thread overview]
Message-ID: <14208.58694.57289.45093@dukat.scot.redhat.com> (raw)
In-Reply-To: <199907021658.KAA22753@webber.adilger.net>
Hi,
On Fri, 2 Jul 1999 10:58:27 -0600 (MDT), Andreas Dilger
<adilger@enel.ucalgary.ca> said:
> I agree that reserving GDT blocks would be a small hack for v0 of ext2, but
> we could add a "COMPATIBLE" extension to v1 of ext2 that gave the number of
> GDT blocks reserved. Also, since the v1 sparse superblock filesystems
> leave a gap between the structures, there should not be a real problem.
> We just have to make sure that we agree (for example) that all the blocks
> from the start of the group to the block bitmap are reserved for the GDT.
> This is not a big strech, since this is already how v0 ext2 filesystems are.
If you're going to be moving user data around anyway (and you have to be
able to do this for the shrink case anyway), then relocating the
inode/bitmap blocks is really not that much harder.
--Stephen
next prev parent reply other threads:[~1999-07-05 17:03 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
1999-06-30 9:46 [linux-lvm] Re: ext2resize Admin
1999-07-02 16:58 ` Andreas Dilger
1999-07-05 17:03 ` Stephen C. Tweedie [this message]
-- strict thread matches above, loose matches on Subject: below --
1999-07-06 8:56 Lennert Buytenhek
1999-07-06 8:47 Lennert Buytenhek
1999-07-06 7:56 Lennert Buytenhek
1999-07-08 14:34 ` tytso
1999-07-08 22:56 ` Theodore Y. Ts'o
1999-07-05 20:49 Andreas Dilger
1999-07-05 19:47 Andreas Dilger
1999-07-07 5:27 ` John Finlay
1999-07-05 8:47 Lennert Buytenhek
1999-07-05 18:38 ` John Finlay
1999-07-05 18:55 ` John Finlay
1999-07-05 8:40 Lennert Buytenhek
1999-07-04 18:56 Andreas Dilger
[not found] <009c01bebee1$aa81b9a0$0102010a@adminstation.sgymsdam.nl>
1999-06-30 7:34 ` Andreas Dilger
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=14208.58694.57289.45093@dukat.scot.redhat.com \
--to=sct@redhat.com \
--cc=adilger@enel.ucalgary.ca \
--cc=linux-fsdevel@vger.rutgers.edu \
--cc=linux-lvm@msede.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;
as well as URLs for NNTP newsgroup(s).