From: Ed Tomlinson <edt@aei.ca>
To: Nikolai Joukov <kolya@cs.sunysb.edu>
Cc: linux-fsdevel@vger.kernel.org, linux-kernel@vger.kernel.org,
linux-raid@vger.kernel.org
Subject: Re: [ANNOUNCE] RAIF: Redundant Array of Independent Filesystems
Date: Fri, 15 Dec 2006 18:58:19 -0500 [thread overview]
Message-ID: <200612151858.19935.edt@aei.ca> (raw)
In-Reply-To: <Pine.GSO.4.53.0612151504360.3466@compserv1>
On Friday 15 December 2006 15:11, Nikolai Joukov wrote:
> > On Wednesday 13 December 2006 12:47, Nikolai Joukov wrote:
> > > We have designed a new stackable file system that we called RAIF:
> > > Redundant Array of Independent Filesystems
> >
> > Do you have a function similar to an an EMC cloneset? Basicily a cloneset
> > tracks what has changed in both the source and target luns (drives). When one
> > updates the cloneset the target is made identical to the source. Its a great
> > way to do backups. Its an important feature to be able to write to the target drives.
> > I would love to see this working at a filesystem level.
>
> Well, if you mount RAIF over your file system and a for-backups file
> system, RAIF can replicate the files on both of them automatically. I
> guess that's what you need.
Yes and no. The idea behind the cloneset is that most of the blocks (or files)
do not change in either source or target. This being the case its only necessary
to update the changed elements. This means updates are incremental. Once
the system has figured out what it needs to update its usable and if you access
an element that should be updated you will see the correctly updated version - even
though backgound resyncing is still in progress. This type of logic is great for backups.
Thanks
Ed Tomlinson
next prev parent reply other threads:[~2006-12-15 23:58 UTC|newest]
Thread overview: 32+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-12-13 17:47 [ANNOUNCE] RAIF: Redundant Array of Independent Filesystems Nikolai Joukov
2006-12-13 19:02 ` Phillip Susi
2006-12-13 19:17 ` Nikolai Joukov
2006-12-13 19:32 ` Nikolai Joukov
2006-12-13 19:33 ` Jan Engelhardt
2006-12-13 19:57 ` Nikolai Joukov
2006-12-13 19:57 ` Al Boldi
2006-12-14 21:01 ` Nikolai Joukov
2006-12-14 21:30 ` Charles Manning
2006-12-15 16:48 ` Nikolai Joukov
2006-12-14 22:48 ` berk walker
2006-12-15 5:02 ` Al Boldi
2006-12-15 17:41 ` Nikolai Joukov
[not found] ` <200612161635.49502.a1426z@gawab.com>
2006-12-16 17:39 ` Nikolai Joukov
2006-12-19 17:50 ` stacked filesystem cache waste Bryan Henderson
[not found] ` <200612172059.07941.a1426z@gawab.com>
2006-12-23 3:21 ` [ANNOUNCE] RAIF: Redundant Array of Independent Filesystems Nikolai Joukov
2006-12-14 11:12 ` Al Boldi
2006-12-14 23:44 ` Nikolai Joukov
2006-12-15 5:03 ` Al Boldi
2006-12-15 18:47 ` Nikolai Joukov
2006-12-15 12:47 ` Ed Tomlinson
2006-12-15 20:11 ` Nikolai Joukov
2006-12-15 23:58 ` Ed Tomlinson [this message]
2006-12-16 0:20 ` Bryan Henderson
2006-12-16 1:20 ` Nikolai Joukov
2006-12-16 14:46 ` Ed Tomlinson
2006-12-16 17:57 ` Nikolai Joukov
2006-12-16 0:02 ` David Lang
2006-12-16 0:58 ` Nikolai Joukov
-- strict thread matches above, loose matches on Subject: below --
2006-12-15 1:13 Nikolai Joukov
[not found] <OF582D7197.D6F604B1-ON88257248.0069CC60-88257248.006AE165@us.ibm.com>
2006-12-25 15:13 ` Nikolai Joukov
2007-01-06 5:17 Chaitanya Patti
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=200612151858.19935.edt@aei.ca \
--to=edt@aei.ca \
--cc=kolya@cs.sunysb.edu \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-raid@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;
as well as URLs for NNTP newsgroup(s).