From: Nikolai Joukov <kolya@cs.sunysb.edu>
To: Jan Engelhardt <jengelh@linux01.gwdg.de>
Cc: linux-fsdevel@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [ANNOUNCE] RAIF: Redundant Array of Independent Filesystems
Date: Wed, 13 Dec 2006 14:57:16 -0500 (EST) [thread overview]
Message-ID: <Pine.GSO.4.53.0612131443180.5969@compserv1> (raw)
In-Reply-To: <Pine.LNX.4.61.0612132031220.32433@yvahk01.tjqt.qr>
> >We have designed a new stackable file system that we called RAIF:
> >Redundant Array of Independent Filesystems.
> >
> >Similar to Unionfs, RAIF is a fan-out file system and can be mounted over
> >many different disk-based, memory, network, and distributed file systems.
> >RAIF can use the stable and maintained code of the other file systems and
> >thus stay simple itself. Similar to standard RAID, RAIF can replicate the
> >data or store it with parity on any subset of the lower file systems. RAIF
> >has three main advantages over traditional driver-level RAID systems:
> >
> >1. RAIF can be mounted over any set of file systems. This allows users to
> > create many more useful configurations. For example, it is possible to
> > replicate the data on the local and remote disks, and stripe the data on
> > the local hard drives and keep the parity (or even ECC to tolerate
> > multiple failures) on the remote server(s). In the latter case, all the
> > read requests will be satisfied from the fast local disks and no local
> > disk space will be spent on parity.
>
> As for striping on a simplistic level, look at the Equal File
> Distribution patch for unionfs :-)
>
> http://www.mail-archive.com/unionfs@mail.fsl.cs.sunysb.edu/msg01936.html
>
> Files are stored normally so that after the union is unmounted, the
> files appear in one piece (unlike real RAID0 over two block devices).
RAIF supports rules that describe how to store particular files or groups
of files. A rule with RAIF level 0 (which is similar to RAID level 0) and
a special striping unit size = '-1' will do the same (distribute the
files on the lower file systems) for files that match any given file name
pattern. A rule with level 4 and striping unit size = '-1' will
distribute files on several file systems and store an extra copy of the
files on a dedicated file system (e.g., an NFS mount with lots of space).
Now guess what RAIF's level 6 will do with a special striping unit
size = '-1' :-)
Nikolai.
----------------
Nikolai Joukov, Ph.D.
Filesystems and Storage Laboratory
Stony Brook University
next prev parent reply other threads:[~2006-12-13 19:57 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 [this message]
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
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=Pine.GSO.4.53.0612131443180.5969@compserv1 \
--to=kolya@cs.sunysb.edu \
--cc=jengelh@linux01.gwdg.de \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@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).