[ANNOUNCE]: reiser4

[ANNOUNCE]: reiser4

[Nikita Danilov]

Hello,

Snapshot of reiser4 source code can be found at 
http://www.namesys.com/snapshots/2002.10.29/.

It is set of patches against current Linus BK tree (2.5.44).

Reiser4 is the next version of ReiserFS file system. It was re-written
from the scratch. It supports:

 - full data journalling with "wandered logs" ("shadows" in DB
   parlance);

 - extent-based files;

 - delayed allocation of disk space and on-line optimization of disk
   layout across file boundaries;

 - plugins: infrastructure for easy extention of file system and utils
   functionality;

 - and a lot more, see http://www.namesys.com/v4/v4.html

Snapshot contains reiser4 proper (fs_reiser4.diff), set of patches
(described in READ.ME) with necessary changes to the core kernel, and
utils package (in particlar, mkfs.reiser4).

It is still crasheable. Do not put critical data on it.

Nikita.

Re: [ANNOUNCE]: reiser4

[Jeff Garzik]

Nikita Danilov wrote:

>Hello,
>
>Snapshot of reiser4 source code can be found at 
>http://www.namesys.com/snapshots/2002.10.29/.
>
>It is set of patches against current Linus BK tree (2.5.44).
>  
>

The current Linus BK tree is quite a bit different from 2.5.44 ;-)

Take a look at 2.5.44-bk1 at 
ftp://ftp.kernel.org/pub/linux/kernel/v2.5/snapshots/

A -bk2 snapshot should appear within the hour, too, with heaps of 
additional changes.

    Jeff

Re: [ANNOUNCE]: reiser4

[Nikita Danilov]

Jeff Garzik writes:
 > Nikita Danilov wrote:
 > 
 > >Hello,
 > >
 > >Snapshot of reiser4 source code can be found at 
 > >http://www.namesys.com/snapshots/2002.10.29/.
 > >
 > >It is set of patches against current Linus BK tree (2.5.44).
 > >  
 > >
 > 
 > The current Linus BK tree is quite a bit different from 2.5.44 ;-)
 > 
 > Take a look at 2.5.44-bk1 at 
 > ftp://ftp.kernel.org/pub/linux/kernel/v2.5/snapshots/
 > 
 > A -bk2 snapshot should appear within the hour, too, with heaps of 
 > additional changes.
 > 

Sorry, my fault.

Patches in reiser4 snapshot are against Linus BK repository at
http://linux.bkbits.net/linux-2.5. Numbers 2, 5, and 44, are, of course,
just VERSION, PATCHLEVEL, and SUBLEVEL in the Makefile of the said
repository.

Probably we should prepare patches against ftp.kernel.org shapshots
instead.

 >     Jeff
 > 

Nikita.

 > 
 > 
 > 

Re: [ANNOUNCE]: reiser4

[Tomas Szepe]

>  > Nikita Danilov wrote:
>  > 
>  > >Hello,
>  > >
>  > >Snapshot of reiser4 source code can be found at 
>  > >http://www.namesys.com/snapshots/2002.10.29/.
>  > >
>  > >It is set of patches against current Linus BK tree (2.5.44).
>  > >  
>  > >
>  > 
>  > The current Linus BK tree is quite a bit different from 2.5.44 ;-)
>  > 
>  > Take a look at 2.5.44-bk1 at 
>  > ftp://ftp.kernel.org/pub/linux/kernel/v2.5/snapshots/
>  > 
>  > A -bk2 snapshot should appear within the hour, too, with heaps of 
>  > additional changes.
>  > 
> 
> Sorry, my fault.
> 
> Patches in reiser4 snapshot are against Linus BK repository at
> http://linux.bkbits.net/linux-2.5. Numbers 2, 5, and 44, are, of course,
> just VERSION, PATCHLEVEL, and SUBLEVEL in the Makefile of the said
> repository.

The following is needed to compile reiser4 in 2.5.44-bk3:

diff -urN linux-2.5.44-bk3-reiser4/mm/Makefile linux-2.5.44-bk3-reiser4.1/mm/Makefile
--- linux-2.5.44-bk3-reiser4/mm/Makefile	2002-10-12 13:35:03.000000000 +0200
+++ linux-2.5.44-bk3-reiser4.1/mm/Makefile	2002-10-30 17:15:10.000000000 +0100
@@ -2,7 +2,7 @@
 # Makefile for the linux memory manager.
 #
 
-export-objs := shmem.o filemap.o mempool.o page_alloc.o page-writeback.o
+export-objs := shmem.o filemap.o mempool.o page_alloc.o page-writeback.o swap.o
 
 obj-y	 := memory.o mmap.o filemap.o mprotect.o mlock.o mremap.o \
 	    vmalloc.o slab.o bootmem.o swap.o vmscan.o page_io.o \
diff -urN linux-2.5.44-bk3-reiser4/mm/swap.c linux-2.5.44-bk3-reiser4.1/mm/swap.c
--- linux-2.5.44-bk3-reiser4/mm/swap.c	2002-10-16 10:53:13.000000000 +0200
+++ linux-2.5.44-bk3-reiser4.1/mm/swap.c	2002-10-30 17:14:23.000000000 +0100
@@ -22,6 +22,7 @@
 #include <linux/mm_inline.h>
 #include <linux/buffer_head.h>
 #include <linux/prefetch.h>
+#include <linux/module.h>
 
 /* How many pages do we try to swap or page in/out together? */
 int page_cluster;
@@ -192,6 +193,7 @@
 		spin_unlock_irq(&zone->lru_lock);
 	__pagevec_release(pvec);
 }
+EXPORT_SYMBOL(pagevec_deactivate_inactive);
 
 /*
  * Add the passed pages to the LRU, then drop the caller's refcount

Re: [ANNOUNCE]: reiser4

[Nikita Danilov]

Tomas Szepe writes:
 > >  > Nikita Danilov wrote:
 > >  > 
 > >  > >Hello,
 > >  > >
 > >  > >Snapshot of reiser4 source code can be found at 
 > >  > >http://www.namesys.com/snapshots/2002.10.29/.
 > >  > >
 > >  > >It is set of patches against current Linus BK tree (2.5.44).
 > >  > >  
 > >  > >
 > >  > 
 > >  > The current Linus BK tree is quite a bit different from 2.5.44 ;-)
 > >  > 
 > >  > Take a look at 2.5.44-bk1 at 
 > >  > ftp://ftp.kernel.org/pub/linux/kernel/v2.5/snapshots/
 > >  > 
 > >  > A -bk2 snapshot should appear within the hour, too, with heaps of 
 > >  > additional changes.
 > >  > 
 > > 
 > > Sorry, my fault.
 > > 
 > > Patches in reiser4 snapshot are against Linus BK repository at
 > > http://linux.bkbits.net/linux-2.5. Numbers 2, 5, and 44, are, of course,
 > > just VERSION, PATCHLEVEL, and SUBLEVEL in the Makefile of the said
 > > repository.
 > 
 > The following is needed to compile reiser4 in 2.5.44-bk3:

Thanks a lot.

 > 
 > diff -urN linux-2.5.44-bk3-reiser4/mm/Makefile linux-2.5.44-bk3-reiser4.1/mm/Makefile
 > --- linux-2.5.44-bk3-reiser4/mm/Makefile	2002-10-12 13:35:03.000000000 +0200
 > +++ linux-2.5.44-bk3-reiser4.1/mm/Makefile	2002-10-30 17:15:10.000000000 +0100
 > @@ -2,7 +2,7 @@
 >  # Makefile for the linux memory manager.
 >  #
 >  

Nikita.

Re: [ANNOUNCE]: reiser4

[Ross Vandegrift]

On Tue, Oct 29, 2002 at 08:45:52PM +0300, Nikita Danilov wrote:
> It is still crasheable. Do not put critical data on it.

How crashable?  I'd like to play around with this on the /home partition
on my personal workstation.

Is it resiliant enough to be used if I have a cron job make backups
every 12 hours?  How about every 2 hours?

Sounds like it'll be cool - thanks for the coolest filesystem on the
planet.

-- 
Ross Vandegrift
ross@willow.seitz.com

A Pope has a Water Cannon.				 It is a Water Cannon.
He fires Holy-Water from it.			    It is a Holy-Water Cannon.
He Blesses it.				       It is a Holy Holy-Water Cannon.
He Blesses the Hell out of it.		It is a Wholly Holy Holy-Water Cannon.
He has it pierced.		  It is a Holey Wholly Holy Holy-Water Cannon.
Batman and Robin arrive.				       He shoots them.

Re: [ANNOUNCE]: reiser4

[Nikita Danilov]

Ross Vandegrift writes:
 > On Tue, Oct 29, 2002 at 08:45:52PM +0300, Nikita Danilov wrote:
 > > It is still crasheable. Do not put critical data on it.
 > 
 > How crashable?  I'd like to play around with this on the /home partition
 > on my personal workstation.

You can untar and compile kernel on it (this exercises file system quite
a bit), run various stress tests (like fsx and fsstress), but not others
(like mongo).

It still has rough corners under memory pressure. Deadlocks are still
possible under highly concurrent access.

 > 
 > Is it resiliant enough to be used if I have a cron job make backups
 > every 12 hours?  How about every 2 hours?

As for using it for your home directory, you have to judge yourself. :-)

Err, one more bit: fsck is non-existent yet, so, if it crashes---data
are lost for ever.

 > 
 > Sounds like it'll be cool - thanks for the coolest filesystem on the
 > planet.
 > 

Nikita.

Re: [ANNOUNCE]: reiser4

[Hans Reiser]

Nikita Danilov wrote:

>  
>
Don't use it for your home directory before it has been out and tested 
for a while.

-- 
Hans