From: Folkert van Heusden <folkert@vanheusden.com>
To: "Theodore Ts'o" <tytso@mit.edu>,
Kyle Moffett <mrmacman_g4@mac.com>,
John Richard Moser <nigelenki@comcast.net>,
linux-kernel@vger.kernel.org
Subject: Re: soft update vs journaling?
Date: Mon, 23 Jan 2006 21:48:30 +0100 [thread overview]
Message-ID: <20060123204830.GF10077@vanheusden.com> (raw)
In-Reply-To: <20060123072447.GA8785@thunk.org>
> You could of course design a filesystem which maintained a reverse map
> data structure, but it would slow the filesystem down since it would
> be a separate data structure that would have to be updated each time
> you allocated or freed a disk block. And the only use for such a data
> structure would be to make shrinking a filesystem more efficient.
> Given that this is generally not a common operation, it seems unlikely
> that a filesystem designer would choose to make this particular
> tradeoff.
Or you could set if switched off by default. E.g. reserve the space for
it and activate it as soon as some magic switch is set in the kernel.
Then some background processs should update it while als keeping track
of current changes. Then when everything is finished, update some flag
to let the resizer know it can do its job.
Folkert van Heusden
--
www.vanheusden.com/recoverdm/ - got an unreadable cd with scratches?
recoverdm might help you recovering data
--------------------------------------------------------------------
Phone: +31-6-41278122, PGP-key: 1F28D8AE, www.vanheusden.com
next prev parent reply other threads:[~2006-01-23 20:48 UTC|newest]
Thread overview: 32+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-01-22 6:42 soft update vs journaling? John Richard Moser
2006-01-22 8:51 ` Jan Engelhardt
2006-01-22 18:40 ` John Richard Moser
2006-01-22 19:05 ` Adrian Bunk
2006-01-22 19:08 ` Arjan van de Ven
2006-01-22 19:25 ` Adrian Bunk
2006-01-24 2:33 ` Jörn Engel
2006-01-22 9:31 ` Theodore Ts'o
2006-01-22 18:54 ` John Richard Moser
2006-01-22 21:02 ` Theodore Ts'o
2006-01-22 22:44 ` Kyle Moffett
2006-01-23 7:24 ` Theodore Ts'o
2006-01-23 13:31 ` Mitchell Blank Jr
2006-01-23 13:33 ` Kyle Moffett
2006-01-23 13:52 ` Antonio Vargas
2006-01-23 16:48 ` Linux VFS architecture questions Kyle Moffett
2006-01-23 17:00 ` Pekka Enberg
2006-01-23 17:50 ` Kyle Moffett
2006-01-23 17:54 ` Randy.Dunlap
2006-01-23 20:48 ` Folkert van Heusden [this message]
2006-01-23 1:02 ` soft update vs journaling? John Richard Moser
2006-01-22 19:50 ` Diego Calleja
2006-01-22 20:39 ` Suleiman Souhlal
2006-01-22 20:50 ` Diego Calleja
2006-01-23 1:00 ` John Richard Moser
2006-01-23 1:09 ` Suleiman Souhlal
2006-01-23 2:09 ` John Richard Moser
2006-01-22 19:26 ` James Courtier-Dutton
2006-01-23 0:06 ` John Richard Moser
2006-01-23 5:32 ` Michael Loftis
2006-01-23 18:52 ` John Richard Moser
2006-01-23 19:32 ` Matthias Andree
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=20060123204830.GF10077@vanheusden.com \
--to=folkert@vanheusden.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mrmacman_g4@mac.com \
--cc=nigelenki@comcast.net \
--cc=tytso@mit.edu \
/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).