From: "Gergely Gábor" <elentirmo.gilgalad-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
To: users-JrjvKiOkagjYtjvyW6yDsg@public.gmane.org
Subject: Re: Garbage Collection Schemes
Date: Thu, 29 Nov 2007 04:11:04 +0100 [thread overview]
Message-ID: <20071129041104.650412ca.elentirmo.gilgalad@gmail.com> (raw)
In-Reply-To: <200711261512.11121.jsa-MJZuZBXGww0Jmq/UkTHWNaxOck334EZe@public.gmane.org>
[-- Attachment #1.1: Type: text/plain, Size: 2289 bytes --]
On Mon, 26 Nov 2007 15:12:10 -0800
John Andersen <jsa-MJZuZBXGww0Jmq/UkTHWNaxOck334EZe@public.gmane.org> wrote:
> I am new to NILFS, so bear with me.
>
> I would like to ask, (without reading the entire archive of messages) if
> any thought to other garbage collection schemes has been contemplated.
>
> For instance: This file system looks like it might be very useful for
> certain types of environments where N sequential revisions of documents
> must be maintained, regardless of the age or how any given document relates
> to other documents.
>
> Checkpoints do not seem to do this.
>
> I would like to see garbage collection options that allow (for example)
> 10 copies retained (of EACH file), each bearing different dates.
>
> Garbage collection would erase the 11th (oldest copy) if, (and only if) the
> other 10 all had different dates. This prevents the situation where one user
> (or rogue process) re-saving a document 15 times a day wipes out all prior
> copies.
>
> An option might be garbage collection not based on a NUMBER of iterations
> but rather a period of time (3 years, 7 years, etc, while still purging same
> date (or same hour, minute, etc) copies.
>
AFAIK there is a protection interval in which GC wont clean up a checkpoint. (maybe i remember badly... and some other LFS fs was that...)
> This type of garbage collection is found almost nowhere, and this
> file system seems to be the closest possible candidate to do this.
>
> There are applications, where a consistent representation of all
> files at a specific point in time (snapshot or checkpoint) is LESS
> important than the ability to roll back individual documents to
> a number of prior iterations or a number of years.
>
> Legal documents, financial records, code version archiving, etc, all
> have these requirements.
>
>
> --
> __________________________
> John Andersen
> Screenio.com
> _______________________________________________
> users mailing list
> users-JrjvKiOkagjYtjvyW6yDsg@public.gmane.org
> https://www.nilfs.org/mailman/listinfo/users
BTW: does/will nilfs support named snapshots?
Best Regards: Gergely Gábor
--
Gergely Gábor <elentirmo.gilgalad-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
[-- Attachment #1.2: Type: application/pgp-signature, Size: 189 bytes --]
[-- Attachment #2: Type: text/plain, Size: 158 bytes --]
_______________________________________________
users mailing list
users-JrjvKiOkagjYtjvyW6yDsg@public.gmane.org
https://www.nilfs.org/mailman/listinfo/users
next prev parent reply other threads:[~2007-11-29 3:11 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-11-26 23:12 Garbage Collection Schemes John Andersen
[not found] ` <200711261512.11121.jsa-MJZuZBXGww0Jmq/UkTHWNaxOck334EZe@public.gmane.org>
2007-11-29 3:11 ` Gergely Gábor [this message]
2007-11-30 0:59 ` Koji Sato
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=20071129041104.650412ca.elentirmo.gilgalad@gmail.com \
--to=elentirmo.gilgalad-re5jqeeqqe8avxtiumwx3w@public.gmane.org \
--cc=users-JrjvKiOkagjYtjvyW6yDsg@public.gmane.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