Re: [ANNOUNCE] RAIF: Redundant Array of Independent Filesystems

> >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

Re: [ANNOUNCE] RAIF: Redundant Array of Independent Filesystems

> > 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

Re: [ANNOUNCE] RAIF: Redundant Array of Independent Filesystems

On Wed, 13 Dec 2006, Nikolai Joukov wrote: 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 sys

Re: [ANNOUNCE] RAIF: Redundant Array of Independent Filesystems

>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 yo

Re: [ANNOUNCE] RAIF: Redundant Array of Independent Filesystems

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 clonese

Re: NFSv4/pNFS possible POSIX I/O API standards

Andreas Dilger wrote: IMHO, once part of the information is optional, why bother making ANY of it required? Consider "ls -s" on a distributed filesystem that has UID+GID mapping. It doesn't actually NEED to return the UID+GID to ls for each file, since it won't be shown, but if that is part of

Re: [ANNOUNCE] RAIF: Redundant Array of Independent Filesystems

> 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 sou

Re: asynchronous locks for cluster exports

On Wed, Dec 06, 2006 at 12:34:10AM -0500, J. Bruce Fields wrote: > We'd like an asynchronous posix locking interface so that we can provide NFS > clients with cluster-coherent locking without blocking lockd while the > filesystem goes off and talks to other nodes. > > So, here's one attempt. It a

Re: [ANNOUNCE] RAIF: Redundant Array of Independent Filesystems

> Nikolai Joukov wrote: > > > > 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: > > > > > > > >

Re: [ANNOUNCE] RAIF: Redundant Array of Independent Filesystems

> Nikolai Joukov wrote: > > > Nikolai Joukov wrote: > > > > We have designed a new stackable file system that we called RAIF: > > > > Redundant Array of Independent Filesystems. > > > > > > Great! > > > > > > > We have performed some benchmarking on a 3GHz PC with 2GB of RAM and > > > > U320 SCSI d

Re: [ANNOUNCE] RAIF: Redundant Array of Independent Filesystems

> On Friday 15 December 2006 10:01, Nikolai Joukov wrote: > > > Nikolai Joukov wrote: > > > > We have designed a new stackable file system that we called RAIF: > > > > Redundant Array of Independent Filesystems. > > > > > > Great! > > Yes, definitely... > > I see the major benefit being in the mobi

Re: [PATCH 0/3] ensure unique i_ino in filesystems without permanent inode numbers (introduction)

Jörn Engel wrote: > On Fri, 15 December 2006 08:05:24 -0500, Jeff Layton wrote: >> Jeff Layton wrote: >>> Apologies for the long email, but I couldn't come up with a way to explain >>> this in fewer words. Many filesystems that are part of the linux kernel >>> have problems with how they have assi

Re: [PATCH 0/3] ensure unique i_ino in filesystems without permanent inode numbers (introduction)

On Fri, 15 December 2006 08:05:24 -0500, Jeff Layton wrote: > Jeff Layton wrote: > > Apologies for the long email, but I couldn't come up with a way to explain > > this in fewer words. Many filesystems that are part of the linux kernel > > have problems with how they have assign out i_ino values: >

Re: [ANNOUNCE] RAIF: Redundant Array of Independent Filesystems

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 tar

Re: [PATCH 0/3] ensure unique i_ino in filesystems without permanent inode numbers (introduction)

Jeff Layton wrote: > Apologies for the long email, but I couldn't come up with a way to explain > this in fewer words. Many filesystems that are part of the linux kernel > have problems with how they have assign out i_ino values: > If there are no further comments/suggestions on this patchset, I'

Re: [PATCH 1/10] lockd: add new export operation for nfsv4/lockd locking

On Thu, Dec 14, 2006 at 06:04:42PM -0500, J. Bruce Fields wrote: > By the way, one other issue I think we'll need to resolve: > > On Wed, Dec 06, 2006 at 12:34:11AM -0500, J. Bruce Fields wrote: > > +/** > > + * vfs_cancel_lock - file byte range unblock lock > > + * @filp: The file to apply the un