Linux FILESYSTEM BENCHMARKS (includes Reiser4).

[Jade]

I do not believe that braking Reiser4 was sabotaged as such,...

It was deliberately sabotaged and that is clear.

Read this and look at the links:

This is what someone who knows said. From here: http://www.phoronix.com/forums/showp...5&postcount=45 (showpost.php?p=27495&postcount=45)

Thanks for the links, you should probably also put a link to the original this is based on (the Wired Blog).

Remember that in the country this takes place (the murder trial), it doesn't matter what you think. It doesn't even matter what the jury itself thinks of the person's character or "acting strangely" (atleast it's not supposed to) - what matters is what you can prove.

Guilt must be proven, a person is innocent until proven guilty in the USA. There has been a lot of conjecture and circumstantial evidence, which does not mean proof at all.

As to the "kernel saboteurs", uhhmmmm. I have been a user of reiserfs3 for years and never noticed all these "issues" that people all of a sudden came up with (after Reiser was arrested).

In fact I never was affected by any sort of corruption or whatnot - in 6+ years of using the filesystem (since 2.4.0)!

ResierFS v4 is something I've wanted to try for a while, but it seems as if everytime I've gone to just do it that I've been "blocked" by one thing or another (boot CD lacks support, kernel patch is broken, developer kernel has bugs, etc.).

The problem was not that I couldn't just use a NameSys patch on my own kernel (I used my own kernel anyway), and do a double install to get the main install up on v4, the issue was that the last time I looked the last patch I could find to be easily hacked to use a recent kernel (one I wanted) did not support compression. That is the sole reason for me wanting to migrate from v3 to v4, is the realtime compression (not for space increase, but for performance increase).

What I can say from my experience personally is this:

there were several reiserfs v4 patches in a certain kernel developer's tree (Andrew Morton's tree) that were not immediately apparant to be broken... but they were/are.

An unnecessary kludge was introduced for NO REASON WHAT-SO-EVER, which was the cause of the corruption.

This developer is a very "big-name" person, and I will not tell you of whom I speak (this is not about flames, and I don't know why he did it i.e. a mistake or misunderstanding or what).

Needless to say however, a lot of people use his patches for bleeding-edge features, mainly because he is supposed to be "dependable" and "official".

So of course, eventually it was noticed - this few lines of code that was unecessarily introduced causing the coruption, and when asked he gave the most unbelievable answer.

Then he proceeded to do a rewrite and what appeared as "cover his tracks".

Anyhow that is what happened. Make of it what you will, but it surely was NOT bitrot or anything so simple...

If you want to look at conspiracy theories, look at who the biggest sponsor was originally. There's your answer right there, and probably what they'd do to "get rid" of the filesystem (have the inventor locked away)

BTW I've never understood the obsession about ext2 and ext3. ext2 was the worst filesystem I've used since the old days of UFS, and the only filesystems I've personally had explode were both ext2/ext3.

I think I'll go install onto v4 now and do whatever necessary to get it done (if that means reintegrating compression back into the latest version then so be it). I want to do some benchmarks and stress-testing

http://linux.50webs.org/

http://linuxhelp.150m.com/jews/saboteurs.htm

http://m.domaindlx.com/LinuxHelp/jews/saboteurs.htm

[StefanHamminga]

Guilt must be proven, a person is innocent until proven guilty in the USA. There has been a lot of conjecture and circumstantial evidence, which does not mean proof at all.
<SNIP>
As to the "kernel saboteurs", uhhmmmm.

Indeed, lots of conjecture and circumstantial evidence in the "kernel saboteurs" case... I say innocent until proven guilty!

[Thetargos]

It was deliberately sabotaged and that is clear.

Read this and look at the links:

This is what someone who knows said. From here: http://www.phoronix.com/forums/showp...5&postcount=45 (showpost.php?p=27495&postcount=45)

Thanks for the links, you should probably also put a link to the original this is based on (the Wired Blog).

Remember that in the country this takes place (the murder trial), it doesn't matter what you think. It doesn't even matter what the jury itself thinks of the person's character or "acting strangely" (atleast it's not supposed to) - what matters is what you can prove.

Guilt must be proven, a person is innocent until proven guilty in the USA. There has been a lot of conjecture and circumstantial evidence, which does not mean proof at all.

As to the "kernel saboteurs", uhhmmmm. I have been a user of reiserfs3 for years and never noticed all these "issues" that people all of a sudden came up with (after Reiser was arrested).

In fact I never was affected by any sort of corruption or whatnot - in 6+ years of using the filesystem (since 2.4.0)!

ResierFS v4 is something I've wanted to try for a while, but it seems as if everytime I've gone to just do it that I've been "blocked" by one thing or another (boot CD lacks support, kernel patch is broken, developer kernel has bugs, etc.).

The problem was not that I couldn't just use a NameSys patch on my own kernel (I used my own kernel anyway), and do a double install to get the main install up on v4, the issue was that the last time I looked the last patch I could find to be easily hacked to use a recent kernel (one I wanted) did not support compression. That is the sole reason for me wanting to migrate from v3 to v4, is the realtime compression (not for space increase, but for performance increase).

What I can say from my experience personally is this:

there were several reiserfs v4 patches in a certain kernel developer's tree (Andrew Morton's tree) that were not immediately apparant to be broken... but they were/are.

An unnecessary kludge was introduced for NO REASON WHAT-SO-EVER, which was the cause of the corruption.

This developer is a very "big-name" person, and I will not tell you of whom I speak (this is not about flames, and I don't know why he did it i.e. a mistake or misunderstanding or what).

Needless to say however, a lot of people use his patches for bleeding-edge features, mainly because he is supposed to be "dependable" and "official".

So of course, eventually it was noticed - this few lines of code that was unecessarily introduced causing the coruption, and when asked he gave the most unbelievable answer.

Then he proceeded to do a rewrite and what appeared as "cover his tracks".

Anyhow that is what happened. Make of it what you will, but it surely was NOT bitrot or anything so simple...

If you want to look at conspiracy theories, look at who the biggest sponsor was originally. There's your answer right there, and probably what they'd do to "get rid" of the filesystem (have the inventor locked away)

BTW I've never understood the obsession about ext2 and ext3. ext2 was the worst filesystem I've used since the old days of UFS, and the only filesystems I've personally had explode were both ext2/ext3.

I think I'll go install onto v4 now and do whatever necessary to get it done (if that means reintegrating compression back into the latest version then so be it). I want to do some benchmarks and stress-testing

http://linux.50webs.org/

http://linuxhelp.150m.com/jews/saboteurs.htm

http://m.domaindlx.com/LinuxHelp/jews/saboteurs.htm

... And to YOU that is evidence?

Hardly, without the code and a couple of diffs that's no evidence, but a testimony, which is not the same. However, suppose that indeed they were trying to avoid association of the OS with a "convicted criminal", so what? "Discrimination"? That one person might be convicted (for whatever reason, that is not the question here) doesn't make his work to be tainted, true. What about his company? Coiuldn't that entity still be working on the feature and maybe change its name to avoid this undesired association? Not because the community (as such) would think of him for the name of the FS, but other users might, which in turn might associate Linux at large with criminals (regardless if true or false)... Is it really that hard for you to draw these conclusions on your own?

By the way only one of the links you provide actually work (linux.50webs.org). I still don't think that it was deliberately done so, and if it was, at least I understand there could be some reasons for it.

[Sleuth]

without the code and a couple of diffs

You clearly did not read the page in question.

The diffs are attached and the kernel code, including morton's, is publicly available.

[pedepy]

first things first, Jade, is that youll want to drop the red fonts. it doesnt help in getting your message across, believe me...

now, why on earth is it that everytime i stumble upon something about Reiser filesystems its always surrounded by an uneasy aura of insanity, persecution, murders and conspiracies?...

the technology sure looks impressive but quite frankly all this is kind of a big turn off..

[Sleuth]

fwhy on earth is it that everytime i stumble upon something about Reiser filesystems its always surrounded by an uneasy aura of insanity, persecution, murders and conspiracies?...

Maybe, because it is.

[joffe]

Lol, I like how the pro-Reiser site is also full of 9/11-'truth' and racist propaganda.

[energyman]

btw, Edward hinted he is trying to go for August/September for inclusion. Hopefully he can do it - because reiser4 rocks. It rocks very, very hard.