Reiser4 for Linux-2.6.36

Reiser4 for Linux-2.6.36

[Edward Shishkin]

Changes since 2.6.35:

. Fixed ->write_end() method: the old one didn't update i_size, and this
  resulted in empty files and "orphan" items. The problem took place only
  for splice users (loop devices, pipe2, etc).

. Implemented ->sync_fs() method of super operations. Since introducing a
  new per-bdi flushing stuff reiser4 wasn't able to perform sync on umount.
  Now such sync is performed by reiser4_sync_fs().

. Fixed an old bug which led to non-deletable directories.

. Fixed an old bug in tail conversion, which led to data corruption when
  running in disk space pressure situations.

Please, find at
http://www.kernel.org/pub/linux/kernel/people/edward/reiser4/reiser4-for-2.6/

Thanks,
Edward.

Re: Reiser4 for Linux-2.6.36

[Matt]

On Sun, Nov 21, 2010 at 2:31 AM, Edward Shishkin
<edward.shishkin@gmail.com> wrote:
> Changes since 2.6.35:
>
> . Fixed ->write_end() method: the old one didn't update i_size, and this
>  resulted in empty files and "orphan" items. The problem took place only
>  for splice users (loop devices, pipe2, etc).
>
> . Implemented ->sync_fs() method of super operations. Since introducing a
>  new per-bdi flushing stuff reiser4 wasn't able to perform sync on umount.
>  Now such sync is performed by reiser4_sync_fs().
>
> . Fixed an old bug which led to non-deletable directories.
>
> . Fixed an old bug in tail conversion, which led to data corruption when
>  running in disk space pressure situations.
>
> Please, find at
> http://www.kernel.org/pub/linux/kernel/people/edward/reiser4/reiser4-for-2.6/
>
> Thanks,
> Edward.
> --
> To unsubscribe from this list: send the line "unsubscribe reiserfs-devel" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at  http://vger.kernel.org/majordomo-info.html
>

Hi Edward,

thank you very much ! :)

Regards

Matt
--
To unsubscribe from this list: send the line "unsubscribe reiserfs-devel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html

Re: Reiser4 for Linux-2.6.36

[dimas]

that sounds good! but as i remember, you've mentioned some issues about 2.6.35
earlier, which were to be fixed. among them there was the troble with loop
devices. how about this? and there was a mail here where author complained about
problems after moving from 34 to 35. is 36 version more stable or it is better
to still rely on 34.7, which works nice for me?

Edward Shishkin пишет:
> Changes since 2.6.35:
> 
> . Fixed ->write_end() method: the old one didn't update i_size, and this
>  resulted in empty files and "orphan" items. The problem took place only
>  for splice users (loop devices, pipe2, etc).
> 
> . Implemented ->sync_fs() method of super operations. Since introducing a
>  new per-bdi flushing stuff reiser4 wasn't able to perform sync on umount.
>  Now such sync is performed by reiser4_sync_fs().
> 
> . Fixed an old bug which led to non-deletable directories.
> 
> . Fixed an old bug in tail conversion, which led to data corruption when
>  running in disk space pressure situations.
> 
> Please, find at
> http://www.kernel.org/pub/linux/kernel/people/edward/reiser4/reiser4-for-2.6/

--
To unsubscribe from this list: send the line "unsubscribe reiserfs-devel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html

Re: Reiser4 for Linux-2.6.36

[Edward Shishkin]

dimas wrote:
> that sounds good! but as i remember, you've mentioned some issues about 2.6.35
> earlier, which were to be fixed. among them there was the troble with loop
> devices. how about this?

yes, this has been fixed in .36

>  and there was a mail here where author complained about
> problems after moving from 34 to 35. is 36 version more stable or it is better
> to still rely on 34.7, which works nice for me?
>   

I think that moving to .36 is a must, however I don't test
released stuff well enough, so, please keep a possibility
to roll back to previous stuff and report, if any problems.

> Edward Shishkin пишет:
>   
>> Changes since 2.6.35:
>>
>> . Fixed ->write_end() method: the old one didn't update i_size, and this
>>  resulted in empty files and "orphan" items. The problem took place only
>>  for splice users (loop devices, pipe2, etc).
>>
>> . Implemented ->sync_fs() method of super operations. Since introducing a
>>  new per-bdi flushing stuff reiser4 wasn't able to perform sync on umount.
>>  Now such sync is performed by reiser4_sync_fs().
>>
>> . Fixed an old bug which led to non-deletable directories.
>>
>> . Fixed an old bug in tail conversion, which led to data corruption when
>>  running in disk space pressure situations.
>>
>> Please, find at
>> http://www.kernel.org/pub/linux/kernel/people/edward/reiser4/reiser4-for-2.6/
>>     
>
>   

--
To unsubscribe from this list: send the line "unsubscribe reiserfs-devel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html

RE: Reiser4 for Linux-2.6.36

[Юрий Заикин]

The bug with building OpenOffice is still there though now it doesn't produce a kernel panic. The build script just randomly fails with IO exceptions. Builds OK on tmpfs so reiser4 is definitely to the culprit.

Re: Reiser4 for Linux-2.6.36

[Edward Shishkin]

Юрий Заикин wrote:
> The bug with building OpenOffice is still there though now it doesn't produce a kernel panic. The build script just randomly fails with IO exceptions.

Is compression enabled (did you format
the partition with "create=ccreg40" option)?

Thanks for the report.
--
To unsubscribe from this list: send the line "unsubscribe reiserfs-devel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html

Re: Reiser4 for Linux-2.6.36

[Edward Shishkin]

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

Edward Shishkin wrote:
> Юрий Заикин wrote:
>   
>> The bug with building OpenOffice is still there though now it doesn't produce a kernel panic. The build script just randomly fails with IO exceptions.
>>     
>
> Is compression enabled (did you format
> the partition with "create=ccreg40" option)?
>
> Thanks for the report.

Ah, I see..
Could you please apply the attached patch?
Does it fix your problem?

Thanks,
Edward.



[-- Attachment #2: reiser4-fix-write_begin.patch --]
[-- Type: text/x-patch, Size: 594 bytes --]

diff -urN linux-2.6.36.orig/fs/reiser4/plugin/file/cryptcompress.c linux-2.6.36/fs/reiser4/plugin/file/cryptcompress.c
--- linux-2.6.36.orig/fs/reiser4/plugin/file/cryptcompress.c	2010-11-22 04:34:19.000000000 +0100
+++ linux-2.6.36/fs/reiser4/plugin/file/cryptcompress.c	2010-11-22 04:39:34.000000000 +0100
@@ -3785,10 +3785,6 @@
 		ClearPageUptodate(page);
 		goto err0;
 	}
-	if (len != PAGE_CACHE_SIZE && !PageUptodate(page)) {
-		ret = RETERR(-EIO);
-		goto err0;
-	}
 	/* Success. All resources (including checkin_mutex)
 	   will be released in ->write_end() */
 	*fsdata = (void *)buf;

RE: Reiser4 for Linux-2.6.36

[Юрий Заикин]

Works, thanks

-----Original Message-----
From: Edward Shishkin [mailto:edward.shishkin@gmail.com] 
Sent: Monday, November 22, 2010 5:54 AM
To: Юрий Заикин
Cc: dimas000@ya.ru; 'Reiserfs mailing list'
Subject: Re: Reiser4 for Linux-2.6.36

Edward Shishkin wrote:
> Юрий Заикин wrote:
>   
>> The bug with building OpenOffice is still there though now it doesn't produce a kernel panic. The build script just randomly fails with IO exceptions.
>>     
>
> Is compression enabled (did you format the partition with 
> "create=ccreg40" option)?
>
> Thanks for the report.

Ah, I see..
Could you please apply the attached patch?
Does it fix your problem?

Thanks,
Edward.



--
To unsubscribe from this list: send the line "unsubscribe reiserfs-devel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html

Re: Reiser4 for Linux-2.6.36

[Simon]

Hello,
first of all thanks for your works!

Now my Problem:
When theres no userspace left, my kernel crashes,
cpu then works hard i think as the fan speed increases,
but i cant move the mouse-cursor and magic-sys-req-keys also dont work
anymore, so i have to do an ACPI-emergency-off then by pressing
powerbutton 6s.
This error especially happens when using vuze.

--
% fsck.reiser4 --print-profile /dev/sda7
Default profile:
create:          "reg40"           (id:0x0 type:0x0)	[Regular file
plugin for creat(2)]
key:             "key_large"       (id:0x1 type:0xb)	[Key plugin]
compress:        "lzo1"            (id:0x0 type:0xc)	[Compression plugin]
compressMode:    "conv"            (id:0x4 type:0xd)	[Compression Mode
plugin]
cluster:         "64K"             (id:0x0 type:0x10)	[Cluster plugin]
hash:            "r5_hash"         (id:0x1 type:0x3)	[Directory entry
hash plugin]
fibration:       "ext_1_fibre"     (id:0x2 type:0x4)	[Key fibration plugin]
formatting:      "smart"           (id:0x2 type:0x5)	[File body
formatting plugin]

--
well just cleaned some diskspace but probably this shows something anyway..
% measurefs.reiser4 -f /dev/sda7
measurefs.reiser4 1.0.7
Copyright (C) 2001-2005 by Hans Reiser, licensing governed by
reiser4progs/COPYING.

Tree statistics ... done


Packing statistics:


  Formatted nodes:    3390.97b (82.79%)
  Branch nodes:       1049.52b (25.62%)
  Twig nodes:         2575.07b (62.87%)
  Leaf nodes:         3807.24b (92.95%)

Node statistics:
  Total nodes:       23135597
  Formatted nodes:     200158
  Unformatted nodes: 22935439
  Branch nodes:           546
  Twig nodes:           11580
  Leaf nodes:        23123471

Item statistics:
  Total items:        1058097
  Nodeptr items:       200157
  Statdata items:     360716
  Direntry items:       46410
  Tail items:          363788
  Extent items:         87026
---


Am 21.11.2010 02:31, schrieb Edward Shishkin:
> Changes since 2.6.35:
> 
> . Fixed ->write_end() method: the old one didn't update i_size, and this
>  resulted in empty files and "orphan" items. The problem took place only
>  for splice users (loop devices, pipe2, etc).
> 
> . Implemented ->sync_fs() method of super operations. Since introducing a
>  new per-bdi flushing stuff reiser4 wasn't able to perform sync on umount.
>  Now such sync is performed by reiser4_sync_fs().
> 
> . Fixed an old bug which led to non-deletable directories.
> 
> . Fixed an old bug in tail conversion, which led to data corruption when
>  running in disk space pressure situations.
> 
> Please, find at
> http://www.kernel.org/pub/linux/kernel/people/edward/reiser4/reiser4-for-2.6/
> 
> 
> Thanks,
> Edward.
> -- 
> To unsubscribe from this list: send the line "unsubscribe
> reiserfs-devel" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at  http://vger.kernel.org/majordomo-info.html

Re: Reiser4 for Linux-2.6.36

[Edward Shishkin]

Simon wrote:
> Hello,
>   

Hello.

> first of all thanks for your works!
>
> Now my Problem:
> When theres no userspace left, my kernel crashes,
> cpu then works hard i think as the fan speed increases,
> but i cant move the mouse-cursor and magic-sys-req-keys also dont work
> anymore, so i have to do an ACPI-emergency-off then by pressing
> powerbutton 6s.
> This error especially happens when using vuze.
>   

Are you sure that you have reiser4-for-2.6.36
stuff applied? The problem has gone for me...
Could you send kernel messages?

Thanks,
Edward.

> --
> % fsck.reiser4 --print-profile /dev/sda7
> Default profile:
> create:          "reg40"           (id:0x0 type:0x0)	[Regular file
> plugin for creat(2)]
> key:             "key_large"       (id:0x1 type:0xb)	[Key plugin]
> compress:        "lzo1"            (id:0x0 type:0xc)	[Compression plugin]
> compressMode:    "conv"            (id:0x4 type:0xd)	[Compression Mode
> plugin]
> cluster:         "64K"             (id:0x0 type:0x10)	[Cluster plugin]
> hash:            "r5_hash"         (id:0x1 type:0x3)	[Directory entry
> hash plugin]
> fibration:       "ext_1_fibre"     (id:0x2 type:0x4)	[Key fibration plugin]
> formatting:      "smart"           (id:0x2 type:0x5)	[File body
> formatting plugin]
>
> --
> well just cleaned some diskspace but probably this shows something anyway..
> % measurefs.reiser4 -f /dev/sda7
> measurefs.reiser4 1.0.7
> Copyright (C) 2001-2005 by Hans Reiser, licensing governed by
> reiser4progs/COPYING.
>
> Tree statistics ... done
>
>
> Packing statistics:
>
>
>   Formatted nodes:    3390.97b (82.79%)
>   Branch nodes:       1049.52b (25.62%)
>   Twig nodes:         2575.07b (62.87%)
>   Leaf nodes:         3807.24b (92.95%)
>
> Node statistics:
>   Total nodes:       23135597
>   Formatted nodes:     200158
>   Unformatted nodes: 22935439
>   Branch nodes:           546
>   Twig nodes:           11580
>   Leaf nodes:        23123471
>
> Item statistics:
>   Total items:        1058097
>   Nodeptr items:       200157
>   Statdata items:     360716
>   Direntry items:       46410
>   Tail items:          363788
>   Extent items:         87026
> ---
>
>
> Am 21.11.2010 02:31, schrieb Edward Shishkin:
>   
>> Changes since 2.6.35:
>>
>> . Fixed ->write_end() method: the old one didn't update i_size, and this
>>  resulted in empty files and "orphan" items. The problem took place only
>>  for splice users (loop devices, pipe2, etc).
>>
>> . Implemented ->sync_fs() method of super operations. Since introducing a
>>  new per-bdi flushing stuff reiser4 wasn't able to perform sync on umount.
>>  Now such sync is performed by reiser4_sync_fs().
>>
>> . Fixed an old bug which led to non-deletable directories.
>>
>> . Fixed an old bug in tail conversion, which led to data corruption when
>>  running in disk space pressure situations.
>>
>> Please, find at
>> http://www.kernel.org/pub/linux/kernel/people/edward/reiser4/reiser4-for-2.6/
>>
>>
>> Thanks,
>> Edward.
>> -- 
>> To unsubscribe from this list: send the line "unsubscribe
>> reiserfs-devel" in
>> the body of a message to majordomo@vger.kernel.org
>> More majordomo info at  http://vger.kernel.org/majordomo-info.html
>>     
>
>   

Re: Reiser4 for Linux-2.6.36

[Simon]

> Are you sure that you have reiser4-for-2.6.36
> stuff applied? The problem has gone for me...

Yep, looked it up in my zsh-history, so i'm sure:
% patch -p1 < ../reiser4-for-2.6.36.patch

> Could you send kernel messages?

I wish i could, but as it seemes the messages from the crash aint saved,
probably because the kernel does crash completely and so not sync anymore.
Anyway i found some messages hours before the crash, probably the bug
depends on them or they have nothing to do with it, but they mention
ext3 and sda7, this is funny, as ext3 is my root-partition on sda1, and
sda7 is my home-partition with reiser4:

Nov 29 20:49:40 localhost kernel: [61364.033613] Pid: 1856, comm:
ent:sda7! Tainted: P            2.6.36-gentoo-r1 #1
Nov 29 20:49:40 localhost kernel: [61364.033617] Call Trace:
Nov 29 20:49:40 localhost kernel: [61364.033627]  [<ffffffff81167775>] ?
ext3_write_inode+0x45/0x50
Nov 29 20:49:40 localhost kernel: [61364.033633]  [<ffffffff810dfbf4>] ?
writeback_single_inode+0x214/0x2a0
Nov 29 20:49:40 localhost kernel: [61364.033637]  [<ffffffff810e0005>] ?
generic_writeback_sb_inodes+0xe5/0x170
Nov 29 20:49:40 localhost kernel: [61364.033640]  [<ffffffff810e09c0>] ?
writeback_inodes_wb+0x140/0x190
Nov 29 20:49:40 localhost kernel: [61364.033644]  [<ffffffff8113b432>] ?
entd_flush+0xa2/0xe0
Nov 29 20:49:40 localhost kernel: [61364.033647]  [<ffffffff8113b59d>] ?
entd+0x12d/0x280
Nov 29 20:49:40 localhost kernel: [61364.033652]  [<ffffffff810561d0>] ?
autoremove_wake_function+0x0/0x30
Nov 29 20:49:40 localhost kernel: [61364.033655]  [<ffffffff8113b470>] ?
entd+0x0/0x280
Nov 29 20:49:40 localhost kernel: [61364.033658]  [<ffffffff8113b470>] ?
entd+0x0/0x280
Nov 29 20:49:40 localhost kernel: [61364.033661]  [<ffffffff81055d56>] ?
kthread+0x96/0xa0
Nov 29 20:49:40 localhost kernel: [61364.033665]  [<ffffffff81003154>] ?
kernel_thread_helper+0x4/0x10
Nov 29 20:49:40 localhost kernel: [61364.033668]  [<ffffffff81055cc0>] ?
kthread+0x0/0xa0
Nov 29 20:49:40 localhost kernel: [61364.033671]  [<ffffffff81003150>] ?
kernel_thread_helper+0x0/0x10

Re: Reiser4 for Linux-2.6.36

[Simon]

Ah, sorry,
finally found the error, it isnt the reiser4, but a buggy network-driver.
Anyway i got some broken files on reiser4
http://paste.pocoo.org/show/318296/ - badblocks and memory seem to be
ok, probably it was a result of the kernel-hang-ups?

Greets
Simon

Am 30.11.2010 17:00, schrieb Simon:
>> Are you sure that you have reiser4-for-2.6.36
>> stuff applied? The problem has gone for me...
> 
> Yep, looked it up in my zsh-history, so i'm sure:
> % patch -p1 < ../reiser4-for-2.6.36.patch
> 
>> Could you send kernel messages?
> 
> I wish i could, but as it seemes the messages from the crash aint saved,
> probably because the kernel does crash completely and so not sync anymore.
> Anyway i found some messages hours before the crash, probably the bug
> depends on them or they have nothing to do with it, but they mention
> ext3 and sda7, this is funny, as ext3 is my root-partition on sda1, and
> sda7 is my home-partition with reiser4:
> 
> Nov 29 20:49:40 localhost kernel: [61364.033613] Pid: 1856, comm:
> ent:sda7! Tainted: P            2.6.36-gentoo-r1 #1
> Nov 29 20:49:40 localhost kernel: [61364.033617] Call Trace:
> Nov 29 20:49:40 localhost kernel: [61364.033627]  [<ffffffff81167775>] ?
> ext3_write_inode+0x45/0x50
> Nov 29 20:49:40 localhost kernel: [61364.033633]  [<ffffffff810dfbf4>] ?
> writeback_single_inode+0x214/0x2a0
> Nov 29 20:49:40 localhost kernel: [61364.033637]  [<ffffffff810e0005>] ?
> generic_writeback_sb_inodes+0xe5/0x170
> Nov 29 20:49:40 localhost kernel: [61364.033640]  [<ffffffff810e09c0>] ?
> writeback_inodes_wb+0x140/0x190
> Nov 29 20:49:40 localhost kernel: [61364.033644]  [<ffffffff8113b432>] ?
> entd_flush+0xa2/0xe0
> Nov 29 20:49:40 localhost kernel: [61364.033647]  [<ffffffff8113b59d>] ?
> entd+0x12d/0x280
> Nov 29 20:49:40 localhost kernel: [61364.033652]  [<ffffffff810561d0>] ?
> autoremove_wake_function+0x0/0x30
> Nov 29 20:49:40 localhost kernel: [61364.033655]  [<ffffffff8113b470>] ?
> entd+0x0/0x280
> Nov 29 20:49:40 localhost kernel: [61364.033658]  [<ffffffff8113b470>] ?
> entd+0x0/0x280
> Nov 29 20:49:40 localhost kernel: [61364.033661]  [<ffffffff81055d56>] ?
> kthread+0x96/0xa0
> Nov 29 20:49:40 localhost kernel: [61364.033665]  [<ffffffff81003154>] ?
> kernel_thread_helper+0x4/0x10
> Nov 29 20:49:40 localhost kernel: [61364.033668]  [<ffffffff81055cc0>] ?
> kthread+0x0/0xa0
> Nov 29 20:49:40 localhost kernel: [61364.033671]  [<ffffffff81003150>] ?
> kernel_thread_helper+0x0/0x10

Re: Reiser4 for Linux-2.6.36

[Edward Shishkin]

Simon wrote:
> Ah, sorry,
> finally found the error, it isnt the reiser4, but a buggy network-driver.
>   


Nup, that was exactly reiser4 badness: it stepped to other journalling
file systems (ext3 in your case). Here is similar bugreport:

http://marc.info/?l=reiserfs-devel&m=129278532029566&w=2

It was fixed, please upgrade your reiser4 stuff:
http://www.kernel.org/pub/linux/kernel/people/edward/reiser4/reiser4-for-2.6/reiser4-for-2.6.36.patch.gz

Sorry that I've forgot to cc you.

Thanks,
Edward.


> Anyway i got some broken files on reiser4
> http://paste.pocoo.org/show/318296/ - badblocks and memory seem to be
> ok, probably it was a result of the kernel-hang-ups?
>
> Greets
> Simon
>
> Am 30.11.2010 17:00, schrieb Simon:
>   
>>> Are you sure that you have reiser4-for-2.6.36
>>> stuff applied? The problem has gone for me...
>>>       
>> Yep, looked it up in my zsh-history, so i'm sure:
>> % patch -p1 < ../reiser4-for-2.6.36.patch
>>
>>     
>>> Could you send kernel messages?
>>>       
>> I wish i could, but as it seemes the messages from the crash aint saved,
>> probably because the kernel does crash completely and so not sync anymore.
>> Anyway i found some messages hours before the crash, probably the bug
>> depends on them or they have nothing to do with it, but they mention
>> ext3 and sda7, this is funny, as ext3 is my root-partition on sda1, and
>> sda7 is my home-partition with reiser4:
>>
>> Nov 29 20:49:40 localhost kernel: [61364.033613] Pid: 1856, comm:
>> ent:sda7! Tainted: P            2.6.36-gentoo-r1 #1
>> Nov 29 20:49:40 localhost kernel: [61364.033617] Call Trace:
>> Nov 29 20:49:40 localhost kernel: [61364.033627]  [<ffffffff81167775>] ?
>> ext3_write_inode+0x45/0x50
>> Nov 29 20:49:40 localhost kernel: [61364.033633]  [<ffffffff810dfbf4>] ?
>> writeback_single_inode+0x214/0x2a0
>> Nov 29 20:49:40 localhost kernel: [61364.033637]  [<ffffffff810e0005>] ?
>> generic_writeback_sb_inodes+0xe5/0x170
>> Nov 29 20:49:40 localhost kernel: [61364.033640]  [<ffffffff810e09c0>] ?
>> writeback_inodes_wb+0x140/0x190
>> Nov 29 20:49:40 localhost kernel: [61364.033644]  [<ffffffff8113b432>] ?
>> entd_flush+0xa2/0xe0
>> Nov 29 20:49:40 localhost kernel: [61364.033647]  [<ffffffff8113b59d>] ?
>> entd+0x12d/0x280
>> Nov 29 20:49:40 localhost kernel: [61364.033652]  [<ffffffff810561d0>] ?
>> autoremove_wake_function+0x0/0x30
>> Nov 29 20:49:40 localhost kernel: [61364.033655]  [<ffffffff8113b470>] ?
>> entd+0x0/0x280
>> Nov 29 20:49:40 localhost kernel: [61364.033658]  [<ffffffff8113b470>] ?
>> entd+0x0/0x280
>> Nov 29 20:49:40 localhost kernel: [61364.033661]  [<ffffffff81055d56>] ?
>> kthread+0x96/0xa0
>> Nov 29 20:49:40 localhost kernel: [61364.033665]  [<ffffffff81003154>] ?
>> kernel_thread_helper+0x4/0x10
>> Nov 29 20:49:40 localhost kernel: [61364.033668]  [<ffffffff81055cc0>] ?
>> kthread+0x0/0xa0
>> Nov 29 20:49:40 localhost kernel: [61364.033671]  [<ffffffff81003150>] ?
>> kernel_thread_helper+0x0/0x10
>>     
>
>
>   

Re: Reiser4 for Linux-2.6.36

[Simon]

>> Ah, sorry,
>> finally found the error, it isnt the reiser4, but a buggy network-driver.
> Nup, that was exactly reiser4 badness: it stepped to other journalling
> file systems (ext3 in your case). Here is similar bugreport:
Well then my kernel has more than one bug, because the network driver IS
also broken :D

> Sorry that I've forgot to cc you.
np, will upgrade my old 2.6.36/reiser4 kernel,
but already changed to 2.6.37/ext4,
but still have some external reiser4 drives,
so waiting for an 2.6.37-patch. ;)

> Thanks,
> Edward.
thx!
Simon

Re: Reiser4 for Linux-2.6.36

[Serkan Kaba]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

On 21-11-2010 03:31, Edward Shishkin wrote:
> Changes since 2.6.35:
>
> . Fixed ->write_end() method: the old one didn't update i_size, and this
>  resulted in empty files and "orphan" items. The problem took place only
>  for splice users (loop devices, pipe2, etc).
I retried testing glib-2.24. The file size attribute is copied
correctly. But the file contents are still not copied. Thus resulting in
an empty file with non-empty filesize.

- -- 
Sincerely,
Serkan KABA
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.16 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/

iEYEARECAAYFAk0N07oACgkQRh6X64ivZaJncgCfQrcVwmBP7oht2Q7qWAiiQsC2
OYoAnRj1y0AxuHZszsQ4rKcF2OB2TOqA
=Rpde
-----END PGP SIGNATURE-----

Re: Reiser4 for Linux-2.6.36

[Edward Shishkin]

Serkan Kaba wrote:
> On 21-11-2010 03:31, Edward Shishkin wrote:
> > Changes since 2.6.35:
>
> > . Fixed ->write_end() method: the old one didn't update i_size, and this
> >  resulted in empty files and "orphan" items. The problem took place only
> >  for splice users (loop devices, pipe2, etc).
> I retried testing glib-2.24. The file size attribute is copied
> correctly. But the file contents are still not copied. Thus resulting in
> an empty file with non-empty filesize.

Are there any kernel complaints?
Did you enable compression?

Thanks,
Edward.

Re: Reiser4 for Linux-2.6.36

[Serkan Kaba]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

On 19-12-2010 18:05, Edward Shishkin wrote:
> Are there any kernel complaints?
dmesg has no clue :(
> Did you enable compression?
No.
> 
> Thanks,
> Edward.
> 
Thanks in advance.
- -- 
Sincerely,
Serkan KABA
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.16 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/

iEYEARECAAYFAk0OL7oACgkQRh6X64ivZaLvogCeLehV0fcDJUAl8VIlyN/+6vQg
zJoAoIRgnONO0MUR83zf/hDECgnPBaO+
=UBP/
-----END PGP SIGNATURE-----

Re: Reiser4 for Linux-2.6.36

[Serkan Kaba]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1



On 19-12-2010 18:15, Serkan Kaba wrote:
> On 19-12-2010 18:05, Edward Shishkin wrote:
>> Are there any kernel complaints?
> dmesg has no clue :(
>> Did you enable compression?
> No.
> 
>> Thanks,
>> Edward.
> 
> Thanks in advance.
- --
Any other way to provide more debug data?
- -- 
Sincerely,
Serkan KABA
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.16 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/

iEYEARECAAYFAk0PlroACgkQRh6X64ivZaJmawCfSLBwo9nmN/TW72/gOHOfmVan
qjMAn3FXQIpxN0OIbwxhlRI6JlR4A4gC
=zZBY
-----END PGP SIGNATURE-----

Re: Reiser4 for Linux-2.6.36

[Edward Shishkin]

Serkan Kaba wrote:
> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
>
>
>
> On 19-12-2010 18:15, Serkan Kaba wrote:
>   
>> On 19-12-2010 18:05, Edward Shishkin wrote:
>>     
>>> Are there any kernel complaints?
>>>       
>> dmesg has no clue :(
>>     
>>> Did you enable compression?
>>>       
>> No.
>>
>>     
>>> Thanks,
>>> Edward.
>>>       
>> Thanks in advance.
>>     
> - --
> Any other way to provide more debug data?
>   

Nop, thanks.

I guess we need to walk along splice(2) path
in reiser4 to figure out why a file gets empty.

I'll take a look a bit later..