From: "John Anthony Kazos Jr." <jakj@j-a-k-j.com>
To: Chris Lee <cslee-list@cybericom.co.uk>
Cc: linux-ext4 <linux-ext4@vger.kernel.org>
Subject: Re: A feature??
Date: Sun, 20 May 2007 07:01:32 -0400 (EDT) [thread overview]
Message-ID: <alpine.DEB.0.99.0705200700040.12765@sigma.j-a-k-j.com> (raw)
In-Reply-To: <46500C02.3010802@cybericom.co.uk>
> I am not a FS guru so please tell me where to get off if I sound stupid.
> After lurking for some time I have come up with something that may be of
> interest as a feature:
>
> If EXT4 were to pr-allocate a configurable amount of space for a special file
> and then use that file as a new EXT4 partition;
> -Use that file for all new writes to disk
> -Any changed files are changed by writing the change to this file, or the
> whole changed file, whichever is more efficient end to end.
> -A section of the file includes tracking of files that need modification in
> the actual FS.
> -Then when the disk is put back into normal read write mode the FS data in the
> file just needs to be worked into the actual FS.
>
> This way the FS could be put into suspended operation while a third party
> reads it.
> I know there are other methods like snapshots, but this works at the FS level
> so that the third party, which obviously needs to know ext4, can access the
> hard drive directly.
Sounds like a combination of loopback and union mounting, except more
automated. Not sure there'd be much benefit to implementing those concepts
redundantly at the filesystem level.
prev parent reply other threads:[~2007-05-20 11:26 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-05-20 8:51 A feature?? Chris Lee
2007-05-20 11:01 ` John Anthony Kazos Jr. [this message]
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=alpine.DEB.0.99.0705200700040.12765@sigma.j-a-k-j.com \
--to=jakj@j-a-k-j.com \
--cc=cslee-list@cybericom.co.uk \
--cc=linux-ext4@vger.kernel.org \
/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