linux-fsdevel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Pradeep Padala <ppadala@eecs.umich.edu>
To: linux-fsdevel@vger.kernel.org
Cc: logfs-devel@lists.sourceforge.net
Subject: [RFC] Log-structured File System for Linux that Supports Snapshots
Date: Fri, 26 Aug 2005 20:03:43 -0400	[thread overview]
Message-ID: <430FADDF.7080307@eecs.umich.edu> (raw)

Hello,
    For past two months, I have been working on developing a 
log-structured file system (LFS) that supports snapshots as a part of 
the Google Summer of Code (SoC) [1] program. The motivation and goals 
for the project are described in my SoC proposal [2].
    In the current state, LFS is quite usable (all the basic fs 
operations are working), and a working cleaner is also available. 
However, it's not yet ready for the heavy iron and I need to sort out a 
few issues. I hope to include it in the mainline, and I will release a 
set of patches later for reviewing.
    Instructions on compiling and using the stable and development 
versions from CVS are available at [3]. The bleeding edge version 
includes basic snapshotting framework.
    The project website is http://logfs.sourceforge.net, and a mailing 
list [4] is available for discussion.
    Comments are welcome.

Thanks,
-- 
Pradeep Padala
http://ppadala.blogspot.com

[1] http://code.google.com/summerofcode.html
[2] http://logfs.sourceforge.net/lfs.pdf
[3] http://logfs.sourceforge.net/compiling.html
[4] http://lists.sourceforge.net/lists/listinfo/logfs-devel

             reply	other threads:[~2005-08-27  0:03 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-08-27  0:03 Pradeep Padala [this message]
2005-08-30  6:55 ` [RFC] Log-structured File System for Linux that Supports Snapshots amagai
2005-08-30 16:15   ` Pradeep Padala
2005-08-31  0:56     ` amagai

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=430FADDF.7080307@eecs.umich.edu \
    --to=ppadala@eecs.umich.edu \
    --cc=linux-fsdevel@vger.kernel.org \
    --cc=logfs-devel@lists.sourceforge.net \
    /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).