[<prev] [next>] [thread-next>] [day] [month] [year] [list]
Message-ID: <Pine.GSO.4.53.0612141828220.8234@compserv1>
Date: Thu, 14 Dec 2006 18:44:18 -0500 (EST)
From: Nikolai Joukov <kolya@...sunysb.edu>
To: Al Boldi <a1426z@...ab.com>
cc: linux-fsdevel@...r.kernel.org, linux-kernel@...r.kernel.org,
linux-raid@...r.kernel.org
Subject: Re: [ANNOUNCE] RAIF: Redundant Array of Independent Filesystems
> > 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
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists