| View previous topic :: View next topic |
| Author |
Message |
20div0
n00b
Joined: 27 Sep 2005
Posts: 20
|
 Posted: Tue Sep 27, 2005 3:33 pm Post subject: Warning: Don't upgrade to 2.6.14-rc1-mm1 if you use reiser4 |
 |
|
Reiser4 had been working for me for a long time but don't ever upgrade to 2.6.14-rc1-mm1 in the portage.
It corrupted my whole filesystem to a point that I have to rebuild my system. rc2-mm1 was out
(but the portage is not up-to-date yet) and fixed some of the problem but I don't have the gut to verify it.
No more reiser4 for me ever. |
|
| Back to top |
|
 |
firephoto
Veteran
Joined: 29 Oct 2003
Posts: 1612
Location: +48° 5' 23.40", -119° 48' 30.00"
|
| Posted: Tue Sep 27, 2005 3:59 pm Post subject: |
|
|
If anyone uses resier4 it's a good idea to follow the mailing list. The reiser4 patches in 2.6.14-rc-mm aren't very good and the ones that work are reported to be pretty slow. They have made a lot of changes and some of those ties reiser4 into the kernel vfs tighter so changes to the vfs can and will affect it's performance. I guess in a way it has mad it easier for external changes to affect reiser4's performance which will probably be an ongoing battle.
I had dropped my reiser4 usage back to the portage tree only since I quit using the amd64-reiser4 install (amd64 was slower than x86 for what I do) and this last week I put my portage tree back on on the reiserfs(3) partition. It's a great filesystem and worked flawlessly but until it gets into the mainline kernel it's going to have trouble keeping up with kernel releases.
_________________
#gentoo-kde on freenode |
|
| Back to top |
|
|
d4rk74m4
Arch/Herd Tester
Joined: 22 Feb 2004
Posts: 151
|
| Posted: Tue Sep 27, 2005 11:18 pm Post subject: |
|
|
| A lot of the changes to reiser4 recently were to appease the kernel guys, reiser4 was attempting to make it into the mainline kernel for 2.6.14. And failed, again. Hans made a comment on the lkml somewhere that the changes that they had to make have badly affected the stability and performance of reiser4.. all in an attempt to keep the kernel nazi's happy *sigh* |
|
| Back to top |
|
|
bollucks
l33t
Joined: 27 Oct 2004
Posts: 606
|
| Posted: Wed Sep 28, 2005 1:19 am Post subject: |
|
|
| Those kernel nazis created linux and got it to the stage it is. Don't be too taken by Hans' politician like advertising. |
|
| Back to top |
|
|
d4rk74m4
Arch/Herd Tester
Joined: 22 Feb 2004
Posts: 151
|
| Posted: Wed Sep 28, 2005 1:37 am Post subject: |
|
|
Hehe, perhaps I should've added a " " to that post (or removed the *sigh*)! The kernel s/nazis/guys/ *are* doing great things, and Hans can be a bit.. over the top at times. |
|
| Back to top |
|
|
firephoto
Veteran
Joined: 29 Oct 2003
Posts: 1612
Location: +48° 5' 23.40", -119° 48' 30.00"
|
| Posted: Wed Sep 28, 2005 1:51 am Post subject: |
|
|
It is the other filesystem devs that complain the loudest though. Competition brings fear I guess.
_________________
#gentoo-kde on freenode |
|
| Back to top |
|
|
mope
Apprentice
Joined: 23 Feb 2003
Posts: 206
|
| Posted: Sat Oct 01, 2005 8:07 am Post subject: |
|
|
whoa, glad I read this post....or should I say glad that r2 didn't compile?
anyway, I received these errors:
| Quote: |
> just wanting to report that reiser4 as a module was not compiling
> anymore. It failed with the following message :
>
> In file included from fs/reiser4/lock.h:15,
> from fs/reiser4/context.h:14,
> from fs/reiser4/debug.c:25:
> fs/reiser4/txnmgr.h: In function `spin_atom_init':
> fs/reiser4/txnmgr.h:512: error: duplicate case value
> fs/reiser4/txnmgr.h:512: error: previously used here
> fs/reiser4/txnmgr.h: In function `spin_txnh_init':
> fs/reiser4/txnmgr.h:513: error: duplicate case value
> fs/reiser4/txnmgr.h:513: error: previously used here
> fs/reiser4/txnmgr.h: In function `spin_txnmgr_init':
> fs/reiser4/txnmgr.h:514: error: duplicate case value
> fs/reiser4/txnmgr.h:514: error: previously used here
> In file included from fs/reiser4/context.h:14,
> from fs/reiser4/debug.c:25:
> fs/reiser4/lock.h: In function `spin_stack_init':
> fs/reiser4/lock.h:198: error: duplicate case value
> fs/reiser4/lock.h:198: error: previously used here
> In file included from fs/reiser4/znode.h:16,
> from fs/reiser4/tree.h:15,
> from fs/reiser4/super.h:9,
> from fs/reiser4/debug.c:26:
> fs/reiser4/jnode.h: In function `spin_jnode_init':
> fs/reiser4/jnode.h:344: error: duplicate case value
> fs/reiser4/jnode.h:344: error: previously used here
> fs/reiser4/jnode.h: In function `spin_jload_init':
> fs/reiser4/jnode.h:348: error: duplicate case value
> fs/reiser4/jnode.h:348: error: previously used here
> In file included from fs/reiser4/super.h:9,
> from fs/reiser4/debug.c:26:
> fs/reiser4/tree.h: In function `spin_epoch_init':
> fs/reiser4/tree.h:169: error: duplicate case value
> fs/reiser4/tree.h:169: error: previously used here
> In file included from fs/reiser4/debug.c:26:
> fs/reiser4/super.h: In function `spin_super_init':
> fs/reiser4/super.h:379: error: duplicate case value
> fs/reiser4/super.h:379: error: previously used here
> make[2]: *** [fs/reiser4/debug.o] Error 1
> make[1]: *** [fs/reiser4] Error 2
> make: *** [fs] Error 2
|
http://lkml.org/lkml/2005/9/29/294
have no idea what's going on and can't find anything here or on google (other than that single post).
guess it's back to 2.6.13 for me... |
|
| Back to top |
|
|
|
Unsupported Software
