From: Nikolai Joukov <kolya@cs.sunysb.edu>
To: Al Boldi <a1426z@gawab.com>
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: Thu, 14 Dec 2006 18:44:18 -0500 (EST) [thread overview]
Message-ID: <Pine.GSO.4.53.0612141828220.8234@compserv1> (raw)
In-Reply-To: <200612141412.30686.a1426z@gawab.com>
> > We started the project in April 2004. Right now I am using it as my
> > /home/kolya file system at home. We believe that at this stage RAIF is
> > mature enough for others to try it out. The code is available at:
> >
> > <ftp://ftp.fsl.cs.sunysb.edu/pub/raif/>
> >
> > The code requires no kernel patches and compiles for a wide range of
> > kernels as a module. The latest kernel we used it for is 2.6.13 and we
> > are in the process of porting it to 2.6.19.
> >
> > We will be happy to hear your back.
>
> When removing a file from the underlying branch, the oops below happens.
> Wouldn't it be possible to just fail the branch instead of oopsing?
This is a known problem of all Linux stackable file systems. Users are
not supposed to change the file systems below mounted stackable file
systems (but they can read them). One of the ways to enforce it is to use
overlay mounts. For example, mount the lower file systems at
/raif/b0 ... /raif/bN and then mount RAIF at /raif. Stackable file
systems recently started getting into the kernel and we hope that there
will be a better solution for this problem in the future. Having said
that, you are right: failing the branch would be the right thing to do.
Nikolai.
---------------------
Nikolai Joukov, Ph.D.
Filesystems and Storage Laboratory
Stony Brook University
next prev parent reply other threads:[~2006-12-14 23:44 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 [this message]
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.0612141828220.8234@compserv1 \
--to=kolya@cs.sunysb.edu \
--cc=a1426z@gawab.com \
--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).