REISER4 snapshot

REISER4 snapshot

[Vladimir V. Saveliev]

Hello

Namesys has issued new reiser4 snapshot (http://thebsh.namesys.com/snapshots/2004.08.04).
It is against 2.6.8-rc2-mm2.
It is mostly bug fixes.
Look at http://thebsh.namesys.com/snapshots/2004.08.04/READ.ME for install instructions

Re: REISER4 snapshot

[Jonathan Briggs]

[-- Attachment #1: Type: text/plain, Size: 433 bytes --]

On Wed, 2004-08-04 at 12:28, Vladimir V. Saveliev wrote:
> Hello
> 
> Namesys has issued new reiser4 snapshot (http://thebsh.namesys.com/snapshots/2004.08.04).
> It is against 2.6.8-rc2-mm2.
> It is mostly bug fixes.
> Look at http://thebsh.namesys.com/snapshots/2004.08.04/READ.ME for install instructions

So, is this is what will be sent to the main kernel as ready-to-go? 
Yay!
-- 
Jonathan Briggs
jbriggs@esoft.com

[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 189 bytes --]

Re: REISER4 snapshot

[mjt]

On Wed, Aug 04, 2004 at 10:28:14PM +0400, Vladimir V. Saveliev wrote:
>
>Namesys has issued new reiser4 snapshot 

HOORAY!

This is the best news in a while :)

When will we see a directory listing by Apache2?-)

And the somewhat gloomy question:
What's the status on Faye's and Phil0u's bugs?

-- 
mjt

Re: REISER4 snapshot

[Philippe Gramoullé]

Hello,

On Wed, 4 Aug 2004 21:34:33 +0300
mjt@nysv.org (Markus Törnqvist) wrote:

  | And the somewhat gloomy question:
  | What's the status on Faye's and Phil0u's bugs?

Well, great news :) With this snapshot, it doesn't crash anymore on mount.

It even survived a bonnie++ and a mongo run as well as umount.

Well done :)

Thanks,

Philippe

REISER4 snapshot

[Vladimir V. Saveliev]

Hello

Namesys has issued new reiser4 snapshot (http://thebsh.namesys.com/snapshots/2004.13.04).
It is against 2.6.8-rc4-mm1.
Most of changes address warnings Andrew Morton made about patches for kernel reiser4 depends on.
Look at http://thebsh.namesys.com/snapshots/2004.13.04/READ.ME for install instructions

PS: well, probably we should not do that on friday, 13

Re: REISER4 snapshot

[Domenico Andreoli]

On Fri, Aug 13, 2004 at 06:23:45PM +0400, Vladimir V. Saveliev wrote:
> Hello

hi

> Namesys has issued new reiser4 snapshot 
> (http://thebsh.namesys.com/snapshots/2004.13.04).
> It is against 2.6.8-rc4-mm1.

user-space tools are thos of 2004.08.09-internal.testing?

-----[ Domenico Andreoli, aka cavok
 --[ http://people.debian.org/~cavok/gpgkey.asc
   ---[ 3A0F 2F80 F79C 678A 8936  4FEE 0677 9033 A20E BC50

Re: REISER4 snapshot

[Vladimir V. Saveliev]

Hello

Domenico Andreoli wrote:
> On Fri, Aug 13, 2004 at 06:23:45PM +0400, Vladimir V. Saveliev wrote:
> 
>>Hello
> 
> 
> hi
> 
> 
>>Namesys has issued new reiser4 snapshot 
>>(http://thebsh.namesys.com/snapshots/2004.13.04).
>>It is against 2.6.8-rc4-mm1.
> 
> 
> user-space tools are thos of 2004.08.09-internal.testing?
> 
ftp.namesys.com/pub/reiser4progs

> -----[ Domenico Andreoli, aka cavok
>  --[ http://people.debian.org/~cavok/gpgkey.asc
>    ---[ 3A0F 2F80 F79C 678A 8936  4FEE 0677 9033 A20E BC50
> 
> 

Re: REISER4 snapshot

[Stefan Schweizer]

> > user-space tools are thos of 2004.08.09-internal.testing?
> > 
> ftp.namesys.com/pub/reiser4progs

Do they include the libaal.patch and the reiser4progs-1.0.0-tree_scan.patch?

Re: REISER4 snapshot

[Vladimir V. Saveliev]

Hello

Stefan Schweizer wrote:
>>>user-space tools are thos of 2004.08.09-internal.testing?
>>>
>>
>>ftp.namesys.com/pub/reiser4progs
> 
> 
> Do they include the libaal.patch and the reiser4progs-1.0.0-tree_scan.patch?
> 
> 

Yes, both are included

Re: REISER4 snapshot

[Domenico Andreoli]

On Fri, Aug 13, 2004 at 06:23:45PM +0400, Vladimir V. Saveliev wrote:
> Hello
> 
> Namesys has issued new reiser4 snapshot 
> (http://thebsh.namesys.com/snapshots/2004.13.04).

hmm... this date looks strange... it is 2004.08.13, right?

-----[ Domenico Andreoli, aka cavok
 --[ http://people.debian.org/~cavok/gpgkey.asc
   ---[ 3A0F 2F80 F79C 678A 8936  4FEE 0677 9033 A20E BC50

Re: REISER4 snapshot

[Vladimir V. Saveliev]

Hello

Domenico Andreoli wrote:
> On Fri, Aug 13, 2004 at 06:23:45PM +0400, Vladimir V. Saveliev wrote:
> 
>>Hello
>>
>>Namesys has issued new reiser4 snapshot 
>>(http://thebsh.namesys.com/snapshots/2004.13.04).
> 
> 
> hmm... this date looks strange... it is 2004.08.13, right?
> 

thanks, fixed

> -----[ Domenico Andreoli, aka cavok
>  --[ http://people.debian.org/~cavok/gpgkey.asc
>    ---[ 3A0F 2F80 F79C 678A 8936  4FEE 0677 9033 A20E BC50
> 
> 

Re: REISER4 snapshot

[Nikita Danilov]

Domenico Andreoli writes:
 > On Fri, Aug 13, 2004 at 06:23:45PM +0400, Vladimir V. Saveliev wrote:
 > > Hello
 > > 
 > > Namesys has issued new reiser4 snapshot 
 > > (http://thebsh.namesys.com/snapshots/2004.13.04).
 > 
 > hmm... this date looks strange... it is 2004.08.13, right?

By special decree of the U.N. all Friday 13th are assigned to special
13th month dedicated to this very purpose, didn't you know? So, it
actually should be 2004.13.02, because this is second Friday 13th in
this year. :-)

Nikita.

 > 
 > -----[ Domenico Andreoli, aka cavok
 >  --[ http://people.debian.org/~cavok/gpgkey.asc
 >    ---[ 3A0F 2F80 F79C 678A 8936  4FEE 0677 9033 A20E BC50
 > 

Re: REISER4 snapshot

[Domenico Andreoli]

On Fri, Aug 13, 2004 at 07:14:40PM +0400, Nikita Danilov wrote:
> Domenico Andreoli writes:
>  > On Fri, Aug 13, 2004 at 06:23:45PM +0400, Vladimir V. Saveliev wrote:
>  > > 
>  > > Namesys has issued new reiser4 snapshot 
>  > > (http://thebsh.namesys.com/snapshots/2004.13.04).
>  > 
>  > hmm... this date looks strange... it is 2004.08.13, right?
> 
> By special decree of the U.N. all Friday 13th are assigned to special
> 13th month dedicated to this very purpose, didn't you know? So, it
> actually should be 2004.13.02, because this is second Friday 13th in
> this year. :-)
> 

lol. this is very very nice :)

-----[ Domenico Andreoli, aka cavok
 --[ http://people.debian.org/~cavok/gpgkey.asc
   ---[ 3A0F 2F80 F79C 678A 8936  4FEE 0677 9033 A20E BC50

reiser4 snapshot

[Nikita Danilov]

Hello,

new reiser4 snapshot (for 2.6.0) is available at the

http://www.namesys.com/snapshots/2003.12.23/

See READ.ME file there for more instructions.

--------------------------------------------------------------------------------
WARNING: WARNING: WARNING: WARNING: WARNING: WARNING: WARNING: WARNING: WARNING:
Don't use Reiser4 in production environments. It is in the debugging stage.

--------------------------------------------------------------------------------
                                    Files:
--------------------------------------------------------------------------------

core.diff                   Modifications to the core part of the kernel
                            necessary for reiser4

reiser4.only.diff.gz        Reiser4 source code as -p1 patch for the kernel
                            source tree, compressed

all.diff.gz                 Above two patches combines and compressed

reiser4.tar.gz              Reiser4 source code. This also contains SCCS data.

broken-out                  core.diff split into separate patches

reiser4progs-0.4.20.tar.gz  reiser4progs: mkfs, fsck, etc.

libaal-0.4.15.tar.gz        libaal library required by reiser4progs

Nikita.

Re: reiser4 snapshot

[Carl-Daniel Hailfinger]

Nikita Danilov wrote:
> Hello,
> 
> new reiser4 snapshot (for 2.6.0) is available at the
> 
> http://www.namesys.com/snapshots/2003.12.23/
> [...]
> broken-out                  core.diff split into separate patches

403 Forbidden
You don't have permission to access /snapshots/2003.12.23/broken-out/ on
this server.


Carl-Daniel
-- 
http://www.hailfinger.org/

Re: reiser4 snapshot

[Nikita Danilov]

Carl-Daniel Hailfinger writes:
 > Nikita Danilov wrote:
 > > Hello,
 > > 
 > > new reiser4 snapshot (for 2.6.0) is available at the
 > > 
 > > http://www.namesys.com/snapshots/2003.12.23/
 > > [...]
 > > broken-out                  core.diff split into separate patches
 > 
 > 403 Forbidden
 > You don't have permission to access /snapshots/2003.12.23/broken-out/ on
 > this server.

Thanks, fixed.

 > 
 > 
 > Carl-Daniel
 > -- 
 > http://www.hailfinger.org/
 > 


Nikita.

Re: reiser4 snapshot

[Viktors Rotanovs]

Nikita Danilov wrote:

>new reiser4 snapshot (for 2.6.0) is available at the
>http://www.namesys.com/snapshots/2003.12.23/
>See READ.ME file there for more instructions.
>  
>
What areas are still not ready for production?
How risky it would be to put, say, 20000 e-mail users (cyrus imap and 
nothing else) on reiser4 partition?
Reiser4 works very very well on my desktop pc, so I'm eager to try it on 
something bigger.

Also, does lack of sendfile in the current snapshot mean that Apache 
will lose in performance when serving from Reiser4 partition?

Best Wishes,
Viktors

Re: reiser4 snapshot

[Nikita Danilov]

Viktors Rotanovs writes:
 > Nikita Danilov wrote:
 > 
 > >new reiser4 snapshot (for 2.6.0) is available at the
 > >http://www.namesys.com/snapshots/2003.12.23/
 > >See READ.ME file there for more instructions.
 > >  
 > >
 > What areas are still not ready for production?
 > How risky it would be to put, say, 20000 e-mail users (cyrus imap and 
 > nothing else) on reiser4 partition?

I wouldn't recommend it, frankly. Reiser4 should first pass through more
extensive testing (first internally, and then in something like -mm, or
-wli) before it will be ready for "production".

 > Reiser4 works very very well on my desktop pc, so I'm eager to try it on 
 > something bigger.

Great.

 > 
 > Also, does lack of sendfile in the current snapshot mean that Apache 
 > will lose in performance when serving from Reiser4 partition?

Hmm, what Apache uses sendfile for?

 > 
 > Best Wishes,
 > Viktors

Nikita.

Re: reiser4 snapshot

[Viktors Rotanovs]

Nikita Danilov wrote:

> > Also, does lack of sendfile in the current snapshot mean that Apache 
> > will lose in performance when serving from Reiser4 partition?
>
> Hmm, what Apache uses sendfile for?


It uses it to send static content to client. Quote from Apache 2 docs:

"In situations where Apache 2.0 can ignore the contents of the file to 
be delivered -- for example, when serving static file content -- it 
normally uses the kernel sendfile support the file if the OS supports 
the |sendfile(2)| operation."

"On most platforms, using sendfile improves performance by eliminating 
separate read and send mechanics."

Best Wishes,
Viktors

Re: reiser4 snapshot

[Nikita Danilov]

Viktors Rotanovs writes:
 > Nikita Danilov wrote:
 > 
 > > > Also, does lack of sendfile in the current snapshot mean that Apache 
 > > > will lose in performance when serving from Reiser4 partition?
 > >
 > > Hmm, what Apache uses sendfile for?
 > 
 > 
 > It uses it to send static content to client. Quote from Apache 2 docs:
 > 
 > "In situations where Apache 2.0 can ignore the contents of the file to 
 > be delivered -- for example, when serving static file content -- it 
 > normally uses the kernel sendfile support the file if the OS supports 
 > the |sendfile(2)| operation."
 > 
 > "On most platforms, using sendfile improves performance by eliminating 
 > separate read and send mechanics."

Current reiser4 will be slower than hypothetical reiser4-with-sendfile,
but not necessary slower than, say, ext3.

 > 
 > Best Wishes,
 > Viktors
 > 

Nikita.

reiser4 snapshot

[Nikita Danilov]

Hello,

new reiser4 snapshot is available at 

http://thebsh.namesys.com/snapshots/2003.08.11/

**********************************************************************
                              WARNING!!! 
                      This code is experimental! 
    WE ARE NOT KIDDING! DO NOT PUT ANY VALUABLE DATA ON REISER4 YET!
**********************************************************************

Lots of changes in this snapshot compared to previous one that was
release over half of year ago.  Everything should be better and more
stable I hope.

Snapshot is released as a patch against linux-2.6.0-test3.

REISER4_NOOPT config option (Disable compiler optimizations for reiser4
code.)  is known to not compile on x86.

The reiser4-kernelonly.diff file represents only required kernel
modifications if you plan to use our reiser4 bk repository. It does not
contains any reiser4 code

The reiser4.diff is full patch with everything included.

With this snapshot reiser4 supports different on-disk format by default,
so you should recreate your reiser4 file systems.

Nikita.

Re: reiser4 snapshot

[Carl-Daniel Hailfinger]

Nikita Danilov wrote:
> Hello,
> 
> new reiser4 snapshot is available at 
> 
> http://thebsh.namesys.com/snapshots/2003.08.11/

+config REISER4_LARGE_KEY
+	bool "Use larger keys on reiser4 tree"
+	depends on REISER4_FS
+	default y
+	---help---
+      Make keys larger and use additional bits to order bodies of files
within
+      a directory in the order of their names, which is what you want
+      normally. If you turn this off, file bodies will be ordered by creation
+      time, which is not optimal for most users.
+
+      Warning: flipping this option makes your file system binary
+      incompatible.

This needs some explanation. What happens if I have two reiser4 fs on my
disk, one written with REISER4_LARGE_KEY, the other one without? Does it
prevent me from mounting both filesystems at the same time? If so, will
this change some time?


Thanks,
Carl-Daniel

Re: reiser4 snapshot

[Nikita Danilov]

Carl-Daniel Hailfinger writes:
 > Nikita Danilov wrote:
 > > Hello,
 > > 
 > > new reiser4 snapshot is available at 
 > > 
 > > http://thebsh.namesys.com/snapshots/2003.08.11/
 > 
 > +config REISER4_LARGE_KEY
 > +	bool "Use larger keys on reiser4 tree"
 > +	depends on REISER4_FS
 > +	default y
 > +	---help---
 > +      Make keys larger and use additional bits to order bodies of files
 > within
 > +      a directory in the order of their names, which is what you want
 > +      normally. If you turn this off, file bodies will be ordered by creation
 > +      time, which is not optimal for most users.
 > +
 > +      Warning: flipping this option makes your file system binary
 > +      incompatible.
 > 
 > This needs some explanation. What happens if I have two reiser4 fs on my
 > disk, one written with REISER4_LARGE_KEY, the other one without? Does it
 > prevent me from mounting both filesystems at the same time? If so, will

Right.

 > this change some time?
 > 

Not likely. Supporting both key assignment algorithms costs too much at
run time. Probably small keys will be just obsoleted.

 > 
 > Thanks,
 > Carl-Daniel
 > 

Nikita.

Re: reiser4 snapshot

[Boris Tschirschwitz]

Hey.

I thought I'd give it a try on 2.6.0-test3-mm1.

Even with 'make mrproper' before compiling, I get the following error
message:

(Is there any interest in such error reports?)

bobele linux # make bzImage
  CHK     include/linux/version.h
  UPD     include/linux/version.h
  Making asm->asm-i386 symlink
  CC      scripts/empty.o
  MKELF   scripts/elfconfig.h
  HOSTCC  scripts/file2alias.o
  HOSTCC  scripts/modpost.o
  HOSTLD  scripts/modpost
  SPLIT   include/linux/autoconf.h -> include/config/*
  CC      arch/i386/kernel/asm-offsets.s
  CHK     include/asm-i386/asm_offsets.h
  UPD     include/asm-i386/asm_offsets.h
  CC      init/main.o
In file included from include/linux/unistd.h:9,
                 from init/main.c:18:
include/asm/unistd.h: In function `reiser4':
include/asm/unistd.h:400: error: `__NR_reiser4' undeclared (first use in this function)
include/asm/unistd.h:400: error: (Each undeclared identifier is reported only once
include/asm/unistd.h:400: error: for each function it appears in.)
make[1]: *** [init/main.o] Error 1
make: *** [init] Error 2


On Mon, 11 Aug 2003 19:57:31 +0400, Nikita Danilov wrote:

> Hello,
> 
> new reiser4 snapshot is available at
> 
> http://thebsh.namesys.com/snapshots/2003.08.11/
> 
> **********************************************************************
>                               WARNING!!!
>                       This code is experimental!
>     WE ARE NOT KIDDING! DO NOT PUT ANY VALUABLE DATA ON REISER4 YET!
> **********************************************************************
> 
> Lots of changes in this snapshot compared to previous one that was release
> over half of year ago.  Everything should be better and more stable I
> hope.
> 
> Snapshot is released as a patch against linux-2.6.0-test3.
> 
> REISER4_NOOPT config option (Disable compiler optimizations for reiser4
> code.)  is known to not compile on x86.
> 
> The reiser4-kernelonly.diff file represents only required kernel
> modifications if you plan to use our reiser4 bk repository. It does not
> contains any reiser4 code
> 
> The reiser4.diff is full patch with everything included.
> 
> With this snapshot reiser4 supports different on-disk format by default,
> so you should recreate your reiser4 file systems.
> 
> Nikita.

Re: reiser4 snapshot

[Oleg Drokin]

Hello!

On Mon, Aug 11, 2003 at 05:32:25PM -0700, Boris Tschirschwitz wrote:

> I thought I'd give it a try on 2.6.0-test3-mm1.
> Even with 'make mrproper' before compiling, I get the following error
> message:
> (Is there any interest in such error reports?)

Yes, there is.

> bobele linux # make bzImage
>   CHK     include/linux/version.h
>   UPD     include/linux/version.h
>   Making asm->asm-i386 symlink
>   CC      scripts/empty.o
>   MKELF   scripts/elfconfig.h
>   HOSTCC  scripts/file2alias.o
>   HOSTCC  scripts/modpost.o
>   HOSTLD  scripts/modpost
>   SPLIT   include/linux/autoconf.h -> include/config/*
>   CC      arch/i386/kernel/asm-offsets.s
>   CHK     include/asm-i386/asm_offsets.h
>   UPD     include/asm-i386/asm_offsets.h
>   CC      init/main.o
> In file included from include/linux/unistd.h:9,
>                  from init/main.c:18:
> include/asm/unistd.h: In function `reiser4':
> include/asm/unistd.h:400: error: `__NR_reiser4' undeclared (first use in this function)
> include/asm/unistd.h:400: error: (Each undeclared identifier is reported only once
> include/asm/unistd.h:400: error: for each function it appears in.)
> make[1]: *** [init/main.o] Error 1
> make: *** [init] Error 2

Hm, this is strange.
__NR_reiser4 is clearly defined in include/asm-i386/unistd.h

Probably you had that part of the patch rejected? Can you please verify?

Bye,
    Oleg

Re: reiser4 snapshot

[Cyrille Chepelov]

Le Tue, Aug 12, 2003, à 10:05:42AM +0400, Oleg Drokin a écrit:
> Hello!
> 
> On Mon, Aug 11, 2003 at 05:32:25PM -0700, Boris Tschirschwitz wrote:
> 
> > I thought I'd give it a try on 2.6.0-test3-mm1.
> > Even with 'make mrproper' before compiling, I get the following error
> > message:
> > (Is there any interest in such error reports?)
> 
> Yes, there is.

I have a problem: reiserfs4progs doesn't seem to pay attention to the
--prefix when it comes to locating libaal. I configured libaal with
--prefix=/scratch/riesling/reiser4-inst and installed it there, then tried
to configure reiserfs4progs with the same prefix, and it still fails to
locate libaal. When I force it a little by prepending the call to
./configure with suitable CFLAGS and LDFLAGS, it goes past locating libaal,
but chokes on locating <aal/aal.h>.

I'll sure get past that, but it's a little annoying, and might get in the
way of distributors (depending on the way they package libaal, ie separately
or merged with the main reiserfs4progs package).

	-- Cyrille

-- 

Re: reiser4 snapshot

[Yury Umanets]

On Tue, 2003-08-12 at 11:22, Cyrille Chepelov wrote:
> Le Tue, Aug 12, 2003, à 10:05:42AM +0400, Oleg Drokin a écrit:
> > Hello!
> > 
Hello,
> > On Mon, Aug 11, 2003 at 05:32:25PM -0700, Boris Tschirschwitz wrote:
> > 
> > > I thought I'd give it a try on 2.6.0-test3-mm1.
> > > Even with 'make mrproper' before compiling, I get the following error
> > > message:
> > > (Is there any interest in such error reports?)
> > 
> > Yes, there is.
> 
> I have a problem: reiserfs4progs doesn't seem to pay attention to the
> --prefix when it comes to locating libaal.

--prefix is not the prefix libraries are looked at. It is the prefix of
where package libraries and includes will be installed.

>  I configured libaal with
> --prefix=/scratch/riesling/reiser4-inst and installed it there, then tried
> to configure reiserfs4progs with the same prefix, and it still fails to
> locate libaal.

You need to let dynamic linker know, that some interesting libraries lie
at some location.

Edit /etc/ld.so.conf and there line /scratch/riesling/reiser4-inst
Or set evn. variable LD_LIBRARY_PATH like the following:

export LD_LIBRARY_PATH=/scratch/riesling/reiser4-inst:$LD_LIBRARY_PATH


>  When I force it a little by prepending the call to
> ./configure with suitable CFLAGS and LDFLAGS, it goes past locating libaal,
> but chokes on locating <aal/aal.h>.
This will be fixed. Thanks. temporary cure is to specify CFLAGS durring
make:

make CFLAGS="-I/scratch/riesling/reiser4-inst/include/aal"

> 
> I'll sure get past that, but it's a little annoying, and might get in the
> way of distributors (depending on the way they package libaal, ie separately
> or merged with the main reiserfs4progs package).
libaal is planed to be used with another similar projects to as it
contains useful utilities like device abstraction, etc.  So, it is
better to have it as separated package. But reiser4progs building may be
automated. 
> 
> 	-- Cyrille
-- 
We're flying high, we're watching the world passes by...

Re: reiser4 snapshot

[Cyrille Chepelov]

Le Tue, Aug 12, 2003, à 11:31:57AM +0400, Yury Umanets a écrit:

> > I have a problem: reiserfs4progs doesn't seem to pay attention to the
> > --prefix when it comes to locating libaal.
> 
> --prefix is not the prefix libraries are looked at. It is the prefix of
> where package libraries and includes will be installed.

yes, of course. However, you saw that it's not the only problem.

> >  When I force it a little by prepending the call to
> > ./configure with suitable CFLAGS and LDFLAGS, it goes past locating libaal,
> > but chokes on locating <aal/aal.h>.
> This will be fixed. Thanks. temporary cure is to specify CFLAGS durring
> make:
> 
> make CFLAGS="-I/scratch/riesling/reiser4-inst/include/aal"

can't be done, as there is no Makefile until configure completes -- and it
can't complete as it doesnt pay attention to things like
	CFLAGS="-I/.../include" ./configure 

I got past that, though.

Another little glitch is that the configure.in explicitly checks for 0.4.8
while the provided libaal is 0.4.9. No biggie, just requires modifying the
configure.in and re-running autoconf (you might want to add a check against
that condition in your pre-upload QA scripts).

	-- Cyrille

-- 

Re: reiser4 snapshot

[Vitaly Fertman]

> Another little glitch is that the configure.in explicitly checks for 0.4.8
> while the provided libaal is 0.4.9. No biggie, just requires modifying the
> configure.in and re-running autoconf (you might want to add a check against
> that condition in your pre-upload QA scripts).

yes, thanks, I have found and fixed it already.
Vitaly Fertman

Re: reiser4 snapshot

[Yury Umanets]

On Tue, 2003-08-12 at 12:02, Cyrille Chepelov wrote:
> Le Tue, Aug 12, 2003, à 11:31:57AM +0400, Yury Umanets a écrit:
> 
> > > I have a problem: reiserfs4progs doesn't seem to pay attention to the
> > > --prefix when it comes to locating libaal.
> > 
> > --prefix is not the prefix libraries are looked at. It is the prefix of
> > where package libraries and includes will be installed.
> 
> yes, of course. However, you saw that it's not the only problem.
> 
> > >  When I force it a little by prepending the call to
> > > ./configure with suitable CFLAGS and LDFLAGS, it goes past locating libaal,
> > > but chokes on locating <aal/aal.h>.
> > This will be fixed. Thanks. temporary cure is to specify CFLAGS durring
> > make:
> > 
> > make CFLAGS="-I/scratch/riesling/reiser4-inst/include/aal"
> 
> can't be done, as there is no Makefile until configure completes -- and it
> can't complete as it doesnt pay attention to things like
> 	CFLAGS="-I/.../include" ./configure 
> 
> I got past that, though.
> 
> Another little glitch is that the configure.in explicitly checks for 0.4.8
> while the provided libaal is 0.4.9. No biggie, just requires modifying the
> configure.in and re-running autoconf (you might want to add a check against
> that condition in your pre-upload QA scripts).

Hello,

Everything is fixed and new snapshot is in
http://thebsh.namesys.com/snapshots/2003.08.11/.

See ./configure --help for new option --with-libaal.


Thanks for reports one more time.

Re: reiser4 snapshot

[Cyrille Chepelov]

Le Tue, Aug 12, 2003, à 12:25:58PM +0400, Yury Umanets a écrit:

> Everything is fixed and new snapshot is in
> http://thebsh.namesys.com/snapshots/2003.08.11/.
> 
> See ./configure --help for new option --with-libaal.

That fixes it, thanks!

It can be debated whether --with-libaal=/foo/bar should imply
LD_LIBRARY_PATH=$LD_LIBRARY_PATH:/foo/bar/lib or not (it doesn't seem it
does right now), but at least it's now possible to build and install
libaal + reiser4progs in a user tree without touching /usr.

	-- Cyrille
-- 

Re: reiser4 snapshot

[Yury Umanets]

On Tue, 2003-08-12 at 13:48, Cyrille Chepelov wrote:
> Le Tue, Aug 12, 2003, à 12:25:58PM +0400, Yury Umanets a écrit:
> 
> > Everything is fixed and new snapshot is in
> > http://thebsh.namesys.com/snapshots/2003.08.11/.
> > 
> > See ./configure --help for new option --with-libaal.
> 
> That fixes it, thanks!

> 
> It can be debated whether --with-libaal=/foo/bar should imply
> LD_LIBRARY_PATH=$LD_LIBRARY_PATH:/foo/bar/lib or not (it doesn't seem it
> does right now), but at least it's now possible to build and install
> libaal + reiser4progs in a user tree without touching /usr.

I guess, it is not the job for configure script, but rather for
user/administrator. At least I don't even one project that do so :)

> 
> 	-- Cyrille

Re: reiser4 snapshot

[Yury Umanets]

On Tue, 2003-08-12 at 13:54, Yury Umanets wrote:
> On Tue, 2003-08-12 at 13:48, Cyrille Chepelov wrote:
> > Le Tue, Aug 12, 2003, à 12:25:58PM +0400, Yury Umanets a écrit:
> > 
> > > Everything is fixed and new snapshot is in
> > > http://thebsh.namesys.com/snapshots/2003.08.11/.
> > > 
> > > See ./configure --help for new option --with-libaal.
> > 
> > That fixes it, thanks!
> 
> > 
> > It can be debated whether --with-libaal=/foo/bar should imply
> > LD_LIBRARY_PATH=$LD_LIBRARY_PATH:/foo/bar/lib or not (it doesn't seem it
> > does right now), but at least it's now possible to build and install
> > libaal + reiser4progs in a user tree without touching /usr.
> 
> I guess, it is not the job for configure script, but rather for
> user/administrator. 


> At least I don't even one project that do so :)

I don't know at least one project, that does so :)
> 
> > 
> > 	-- Cyrille
> 
-- 
We're flying high, we're watching the world passes by...

Re: reiser4 snapshot

[Cyrille Chepelov]

Le Tue, Aug 12, 2003, à 01:54:28PM +0400, Yury Umanets a écrit:
> > It can be debated whether --with-libaal=/foo/bar should imply
> > LD_LIBRARY_PATH=$LD_LIBRARY_PATH:/foo/bar/lib or not (it doesn't seem it

> I guess, it is not the job for configure script, but rather for
> user/administrator. At least I don't even one project that do so :)

fair enough

I successfully built 2.6.0-test3 with yesterday's patch. I don't know when
I'll be able to give it a spin, but at least here's some partial 
progress/success feedback, FWIW.
	
	-- Cyrille

-- 

Re: reiser4 snapshot

[Yury Umanets]

On Tue, 2003-08-12 at 15:44, Cyrille Chepelov wrote:
> Le Tue, Aug 12, 2003, à 01:54:28PM +0400, Yury Umanets a écrit:
> > > It can be debated whether --with-libaal=/foo/bar should imply
> > > LD_LIBRARY_PATH=$LD_LIBRARY_PATH:/foo/bar/lib or not (it doesn't seem it
> 
> > I guess, it is not the job for configure script, but rather for
> > user/administrator. At least I don't even one project that do so :)
> 
> fair enough
> 
> I successfully built 2.6.0-test3 with yesterday's patch. I don't know when
> I'll be able to give it a spin, but at least here's some partial 
> progress/success feedback, FWIW.
> 	
> 	-- Cyrille

Thanks Cyrille.
-- 
We're flying high, we're watching the world passes by...

Re: reiser4 snapshot

[Yury Umanets]

On Tue, 2003-08-12 at 11:22, Cyrille Chepelov wrote:
> Le Tue, Aug 12, 2003, à 10:05:42AM +0400, Oleg Drokin a écrit:
> > Hello!
> > 
> > On Mon, Aug 11, 2003 at 05:32:25PM -0700, Boris Tschirschwitz wrote:
> > 
> > > I thought I'd give it a try on 2.6.0-test3-mm1.
> > > Even with 'make mrproper' before compiling, I get the following error
> > > message:
> > > (Is there any interest in such error reports?)
> > 
> > Yes, there is.
> 
> I have a problem: reiserfs4progs doesn't seem to pay attention to the
> --prefix when it comes to locating libaal. I configured libaal with
> --prefix=/scratch/riesling/reiser4-inst and installed it there, then tried
> to configure reiserfs4progs with the same prefix, and it still fails to
> locate libaal. When I force it a little by prepending the call to
> ./configure with suitable CFLAGS and LDFLAGS, it goes past locating libaal,
> but chokes on locating <aal/aal.h>.
> 
> I'll sure get past that, but it's a little annoying, and might get in the
> way of distributors (depending on the way they package libaal, ie separately
> or merged with the main reiserfs4progs package).
> 
> 	-- Cyrille

The problem can't be eliminated just by fixing dynamic linker. 
Will be fixed soon. 

Thanks for report.

Re: reiser4 snapshot

[Boris Tschirschwitz]

Today I tried applying the patch to 2.6.0-test3-mm2, and, yes, some
patches failed. I'll just append the output for the failed hunks.
I guess it gets less surprising the more we get away from 'mm0'.

Boris.

bobele linux # patch -p 1 < ../reiser4.diff
patching file arch/i386/kernel/entry.S
Hunk #1 FAILED at 878.
1 out of 1 hunk FAILED -- saving rejects to file arch/i386/kernel/entry.S.rej
patching file fs/Kconfig
patching file fs/Makefile
Hunk #1 FAILED at 86.
1 out of 1 hunk FAILED -- saving rejects to file fs/Makefile.rej
patching file fs/buffer.c
Hunk #1 succeeded at 262 (offset 37 lines).
patching file fs/fs-writeback.c
patching file fs/inode.c
Hunk #1 succeeded at 990 (offset 2 lines).
Hunk #2 succeeded at 1017 (offset 2 lines).
patching file fs/jbd/transaction.c
patching file fs/sysfs/inode.c
patching file include/asm-i386/unistd.h
Hunk #1 FAILED at 277.
Hunk #2 succeeded at 398 (offset 3 lines).
1 out of 2 hunks FAILED -- saving rejects to file include/asm-i386/unistd.h.rej
patching file include/linux/fs.h
Hunk #2 succeeded at 861 (offset 6 lines).
Hunk #3 succeeded at 1233 (offset 6 lines).
patching file include/linux/init_task.h
Hunk #1 FAILED at 107.
1 out of 1 hunk FAILED -- saving rejects to file include/linux/init_task.h.rej


On Tue, 12 Aug 2003 10:05:42 +0400, Oleg Drokin wrote:

> Hello!
> 
> On Mon, Aug 11, 2003 at 05:32:25PM -0700, Boris Tschirschwitz wrote:
> 
>> I thought I'd give it a try on 2.6.0-test3-mm1. Even with 'make
>> mrproper' before compiling, I get the following error message:
>> (Is there any interest in such error reports?)
> 
> Yes, there is.
> 
>> bobele linux # make bzImage
>>   CHK     include/linux/version.h
>>   UPD     include/linux/version.h
>>   Making asm->asm-i386 symlink
>>   CC      scripts/empty.o
>>   MKELF   scripts/elfconfig.h
>>   HOSTCC  scripts/file2alias.o
>>   HOSTCC  scripts/modpost.o
>>   HOSTLD  scripts/modpost
>>   SPLIT   include/linux/autoconf.h -> include/config/* CC     
>>   arch/i386/kernel/asm-offsets.s CHK     include/asm-i386/asm_offsets.h
>>   UPD     include/asm-i386/asm_offsets.h CC      init/main.o
>> In file included from include/linux/unistd.h:9,
>>                  from init/main.c:18:
>> include/asm/unistd.h: In function `reiser4': include/asm/unistd.h:400:
>> error: `__NR_reiser4' undeclared (first use in this function)
>> include/asm/unistd.h:400: error: (Each undeclared identifier is reported
>> only once include/asm/unistd.h:400: error: for each function it appears
>> in.) make[1]: *** [init/main.o] Error 1
>> make: *** [init] Error 2
> 
> Hm, this is strange.
> __NR_reiser4 is clearly defined in include/asm-i386/unistd.h
> 
> Probably you had that part of the patch rejected? Can you please verify?
> 
> Bye,
>     Oleg

Re: reiser4 snapshot

[Henning Westerholt]

Am Montag, 11. August 2003 17:57 schrieb Nikita Danilov:
> Hello,
>
> new reiser4 snapshot is available at
>
> http://thebsh.namesys.com/snapshots/2003.08.11/
>

Hi,

thank you for the snapshot.

I've tested the reiser4.diff patch, it apply cleanly on my system. 

1)
The option "CONFIG_REISER4_FS_SYSCALL" breaks the build on my system.

[...]
  CC      fs/reiser4/sys_reiser4.o
In file included from include/asm/hardirq.h:6,
                 from include/linux/interrupt.h:10,
                 from include/asm/highmem.h:24,
                 from include/linux/highmem.h:14,
                 from include/linux/pagemap.h:10,
                 from fs/reiser4/sys_reiser4.c:15:
include/linux/irq.h:69: warning: size of `irq_desc' is 28672 bytes
fs/reiser4/sys_reiser4.c:45:27: parser/parser.h: file not found
fs/reiser4/sys_reiser4.c:54:32: parser/parser.code.c: file not found
fs/reiser4/sys_reiser4.c: In function `sys_reiser4':
fs/reiser4/sys_reiser4.c:75: warning: implicit declaration of function 
`reiser4_pars_init'
fs/reiser4/sys_reiser4.c:75: warning: assignment makes pointer from integer 
without a cast
fs/reiser4/sys_reiser4.c:80: dereferencing pointer to incomplete type
fs/reiser4/sys_reiser4.c:81: warning: implicit declaration of function 
`PTRACE'
fs/reiser4/sys_reiser4.c:82: warning: implicit declaration of function 
`yyparse'
fs/reiser4/sys_reiser4.c:83: warning: implicit declaration of function 
`reiser4_pars_free'
fs/reiser4/sys_reiser4.c:66: warning: unused variable `Gencode'
make[2]: *** [fs/reiser4/sys_reiser4.o] Error 1
make[1]: *** [fs/reiser4] Error 2
make: *** [fs] Error 2


2)
Without this option the build finish, but it gave also many warnings about a 
include from include/asm/hardirq.h


3)
I'm also unable to build reiser4 as module:
[...]
include/linux/irq.h:69: warning: size of `irq_desc' is 28672 bytes
  LD [M]  fs/reiser4/reiser4.o
  LD      fs/built-in.o
  GEN     .version
  CHK     include/linux/compile.h
  UPD     include/linux/compile.h
  CC      init/version.o
  LD      init/built-in.o
  LD      .tmp_vmlinux1
arch/i386/kernel/built-in.o(.data+0x7c0): In function `sys_call_table':
: undefined reference to `sys_reiser4'
make: *** [.tmp_vmlinux1] Error 1


Are this know issues?


Henning

Re: reiser4 snapshot

[Nikita Danilov]

Henning Westerholt writes:
 > Am Montag, 11. August 2003 17:57 schrieb Nikita Danilov:
 > > Hello,
 > >
 > > new reiser4 snapshot is available at
 > >
 > > http://thebsh.namesys.com/snapshots/2003.08.11/
 > >
 > 
 > Hi,
 > 
 > thank you for the snapshot.
 > 
 > I've tested the reiser4.diff patch, it apply cleanly on my system. 
 > 
 > 1)
 > The option "CONFIG_REISER4_FS_SYSCALL" breaks the build on my system.

Disable it. We should disable it by default, it seems.

 > 
 > [...]
 >   CC      fs/reiser4/sys_reiser4.o
 > In file included from include/asm/hardirq.h:6,
 >                  from include/linux/interrupt.h:10,
 >                  from include/asm/highmem.h:24,
 >                  from include/linux/highmem.h:14,
 >                  from include/linux/pagemap.h:10,
 >                  from fs/reiser4/sys_reiser4.c:15:
 > include/linux/irq.h:69: warning: size of `irq_desc' is 28672 bytes
 > fs/reiser4/sys_reiser4.c:45:27: parser/parser.h: file not found
 > fs/reiser4/sys_reiser4.c:54:32: parser/parser.code.c: file not found
 > fs/reiser4/sys_reiser4.c: In function `sys_reiser4':
 > fs/reiser4/sys_reiser4.c:75: warning: implicit declaration of function 
 > `reiser4_pars_init'
 > fs/reiser4/sys_reiser4.c:75: warning: assignment makes pointer from integer 
 > without a cast
 > fs/reiser4/sys_reiser4.c:80: dereferencing pointer to incomplete type
 > fs/reiser4/sys_reiser4.c:81: warning: implicit declaration of function 
 > `PTRACE'
 > fs/reiser4/sys_reiser4.c:82: warning: implicit declaration of function 
 > `yyparse'
 > fs/reiser4/sys_reiser4.c:83: warning: implicit declaration of function 
 > `reiser4_pars_free'
 > fs/reiser4/sys_reiser4.c:66: warning: unused variable `Gencode'
 > make[2]: *** [fs/reiser4/sys_reiser4.o] Error 1
 > make[1]: *** [fs/reiser4] Error 2
 > make: *** [fs] Error 2
 > 
 > 
 > 2)
 > Without this option the build finish, but it gave also many warnings about a 
 > include from include/asm/hardirq.h

Something about structure being XXXXX bytes? Ignore them.

 > 
 > 
 > 3)
 > I'm also unable to build reiser4 as module:
 > [...]
 > include/linux/irq.h:69: warning: size of `irq_desc' is 28672 bytes
 >   LD [M]  fs/reiser4/reiser4.o
 >   LD      fs/built-in.o
 >   GEN     .version
 >   CHK     include/linux/compile.h
 >   UPD     include/linux/compile.h
 >   CC      init/version.o
 >   LD      init/built-in.o
 >   LD      .tmp_vmlinux1
 > arch/i386/kernel/built-in.o(.data+0x7c0): In function `sys_call_table':
 > : undefined reference to `sys_reiser4'
 > make: *** [.tmp_vmlinux1] Error 1
 > 
 > 
 > Are this know issues?

Yes. Does it build as module with CONFIG_REISER4_FS_SYSCALL off?

 > 
 > 
 > Henning
 > 

Nikita.

Re: reiser4 snapshot

[Henning Westerholt]

Am Dienstag, 12. August 2003 10:56 schrieb Nikita Danilov
>  > [know issues]
>  > 3)
>  > I'm also unable to build reiser4 as module:
>  > [...]
>  > include/linux/irq.h:69: warning: size of `irq_desc' is 28672 bytes
>  >   LD [M]  fs/reiser4/reiser4.o
>  >   LD      fs/built-in.o
>  >   GEN     .version
>  >   CHK     include/linux/compile.h
>  >   UPD     include/linux/compile.h
>  >   CC      init/version.o
>  >   LD      init/built-in.o
>  >   LD      .tmp_vmlinux1
>  >
>  > arch/i386/kernel/built-in.o(.data+0x7c0): In function `sys_call_table':
>  > : undefined reference to `sys_reiser4'
>  >
>  > make: *** [.tmp_vmlinux1] Error 1
>  >
>  >
>  > Are this know issues?
>
> Yes. Does it build as module with CONFIG_REISER4_FS_SYSCALL off?
>
> Nikita.

No, it doesn't build with the following options:

CONFIG_REISER4_FS=m
# CONFIG_REISER4_FS_SYSCALL is not set
CONFIG_REISER4_LARGE_KEY=y
# CONFIG_REISER4_CHECK is not set
# CONFIG_REISER4_USE_EFLUSH is not set
# CONFIG_REISER4_BADBLOCKS is not set

**
uname -rvmpio
2.6.0-test3-reiserfs4 #4 Tue Aug 12 02:59:22 CEST 2003 i686 AMD Athlon(tm) XP 
1900+ AuthenticAMD GNU/Linux
**
gcc version 3.2.3 20030422 (Gentoo Linux 1.4 3.2.3-r1, propolice)
**
Gentoo 1.4 Stable


Henning

Re: reiser4 snapshot

[Oleg Drokin]

Hello!

On Tue, Aug 12, 2003 at 10:28:07AM +0200, Henning Westerholt wrote:
> > new reiser4 snapshot is available at
> > http://thebsh.namesys.com/snapshots/2003.08.11/
> thank you for the snapshot.
> I've tested the reiser4.diff patch, it apply cleanly on my system. 
> 1)
> The option "CONFIG_REISER4_FS_SYSCALL" breaks the build on my system.

It seems one necessary directory was not included in the patch and that broke build
with CONFIG_REISER4_FS_SYSCALL.
Also we have some 64bit problems reports, so I am going to investigate those and may be we will release
new snapshot with 64 bit fixes and parser directory inplace.

> include/linux/irq.h:69: warning: size of `irq_desc' is 28672 bytes
>   LD [M]  fs/reiser4/reiser4.o
>   LD      fs/built-in.o
>   GEN     .version
>   CHK     include/linux/compile.h
>   UPD     include/linux/compile.h
>   CC      init/version.o
>   LD      init/built-in.o
>   LD      .tmp_vmlinux1
> arch/i386/kernel/built-in.o(.data+0x7c0): In function `sys_call_table':
> : undefined reference to `sys_reiser4'

hm.
I will take a look.
Thank you.

Bye,
    Oleg