thanks for removing super.c:read_bitmaps

2007-01-24 Thread Stefan Traby
Hi!

Thanks for removing super.c:read_bitmaps (2.6.19) - it really
speeds up mounting and is more fair.

-- 

  ciao - 
Stefan


Re: Reiser4 terribly slow

2007-01-24 Thread Xu CanHao

AFAIK, vim fsyncs, azureus fsyncs, and may be many other applications
fsyncs but not only databases.

Definitly turn off fsync() is a bad idea. I just wonder how bad r4's
fsync() performance is.

It seems the result is: disabled fsync() r4 is even slower than
enabled fsync() ext3.o

Is it never be possible to improve that? I found in the mailing-list
that Hans talked it for many years. this must be a CRITICAL
performance flaw for r4.

2007/1/25, [EMAIL PROTECTED] [EMAIL PROTECTED]:

On Wed, 24 Jan 2007 22:05:53 +0800, Xu CanHao said:
 extremely low performance, i managed to turn off fsync() in
 fs/reiser4/plugin/file/file.c (nullify the sync_unix_file() function),

(Maybe you understand the following, if so, feel free to ignore.  I'm
mostly making sure the list archives have this note so anybody else tempted
to do this will think twice)...

Note that this can be *very* dangerous to the health of your database
if you implement it blindly without understanding the *full* implications.

Basically, applications almost never call fsync() unless they need it for
database consistency.  A system crash at an inopportune time *will* totally
ruin your database.





Re: linux-2.6.20-rc4-mm1 Reiser4 filesystem freeze and corruption

2007-01-24 Thread Vince

Vladimir V. Saveliev wrote:

Hello

On Tuesday 23 January 2007 10:38, Vince wrote:

[...]
I don't know if it is related, but I've had the following BUG on 
2.6.20-rc4-mm1 (+ hot-fixes patches applied) :


---
kernel BUG at fs/reiser4/plugin/item/extent_file_ops.c:973!


This is another problem than Zan's one. The attached patch should fix it.

Andrew, please apply.


From: Vladimir Saveliev [EMAIL PROTECTED]

remove_suid may open a transaction in reiser4 which is to be restarted
before entering into main write loop.

Signed-off-by: Vladimir Saveliev [EMAIL PROTECTED]


I'm pleased to confirm I wasn't able to reproduce the bug with your 
patch applied.


Regards,

Vince