Nick Piggin wrote:
Hans Reiser wrote:
So why is the code in the kernel so hard to read then?
Linux kernel code is getting better, and Andrew Morton's code is
especially good, but for the most part it's unnecessarily hard to
read. Look at the elevator code for instance. Ugh.
What's
Hello,
this morning we find our machine with many processes in disk-sleep mode.
They all try to write to one disk but they seem to wait forever.
Even kreiserfsd has status DW.
Is it possible to recover from this situation on do we need to reboot
the machine ?
Our Kernel is 2.4.19-64GB-SMP (
Hi!
V3 is obsoleted by V4 in every way. V3 is old code that should be
marked as deprecated as soon as V4 has passed mass testing. V4 is far
superior in its coding style also. Having V3 in and V4 out is at this
point just stupid.
Really? Last time I checked, even V3's fsck was not too
Nick Piggin wrote:
On Mon, 2005-09-19 at 23:28 -0700, Hans Reiser wrote:
Nick Piggin wrote:
What's wrong with the elevator code?
The name for one. There is no elevator algorithm anywhere in it. There
is a least block number first algorithm that was called an elevator,
Horst von Brand wrote:
Care to give names?
Not publicly, no. If akpm or Linus asks, I will happily encourage
either of them to try to win him back.
who decided to work on BSD
because they had too much dignity to develop a filesystem for Linux.
CC list trimmed.
On Tue, 2005-09-20 at 00:59 -0700, Hans Reiser wrote:
Nick Piggin wrote:
On Mon, 2005-09-19 at 23:28 -0700, Hans Reiser wrote:
Well the terminology changed to io scheduler now, however the
residual elevator name found in places doesn't cause anyone
any problems and
Stephen Pollei writes:
On 9/19/05, Horst von Brand [EMAIL PROTECTED] wrote:
Nikita Danilov [EMAIL PROTECTED] wrote:
It's other way around: declaration is guarded by the preprocessor
conditional so that nobody accidentally use znode_is_loaded() outside of
the debugging mode.
On Tue, Sep 20 2005, Hans Reiser wrote:
The name for one. There is no elevator algorithm anywhere in it. There
is a least block number first algorithm that was called an elevator, but
Well the terminology changed to io scheduler now, however the
residual elevator name found in
On Tuesday 20 September 2005 13:42, Jens Axboe wrote:
On Tue, Sep 20 2005, Hans Reiser wrote:
The name for one. There is no elevator algorithm anywhere in it. There
is a least block number first algorithm that was called an elevator, but
Well the terminology changed to io
Hello again,
I am currently re-installing my linux system and I would like to use
reiser4 since I think its really powerful and great (and is well
written too ;) ).
However, will it be possible to convert a non-compressed reiser4
partition to a compressed one withought the need of deleting data
On Tue, Sep 20 2005, Lorenzo Allegrucci wrote:
On Tuesday 20 September 2005 13:42, Jens Axboe wrote:
On Tue, Sep 20 2005, Hans Reiser wrote:
The name for one. There is no elevator algorithm anywhere in it. There
is a least block number first algorithm that was called an elevator, but
Lorenzo Allegrucci [EMAIL PROTECTED] writes:
[...]
Why not just rename the kernel option elevator to iosched ?
At least update Documentation/kernel-parameters.txt to be consistent,
but I think kernel boot options are considered to be a part of the user
space API and, as such, cannot be
Clemens Eisserer wrote:
Hello again,
I am currently re-installing my linux system and I would like to use
reiser4 since I think its really powerful and great (and is well
written too ;) ).
However, will it be possible to convert a non-compressed reiser4
partition to a compressed one withought
Pavel Machek wrote:
Hi!
V3 is obsoleted by V4 in every way. V3 is old code that should be
marked as deprecated as soon as V4 has passed mass testing. V4 is far
superior in its coding style also. Having V3 in and V4 out is at this
point just stupid.
Really? Last time I checked, even
On Tue, 20 Sep 2005, Lorenzo Allegrucci wrote:
On Tuesday 20 September 2005 13:42, Jens Axboe wrote:
On Tue, Sep 20 2005, Hans Reiser wrote:
The name for one. There is no elevator algorithm anywhere in it. There
is a least block number first algorithm that was called an elevator, but
Nikita Danilov [EMAIL PROTECTED] wrote:
Stephen Pollei writes:
On 9/19/05, Horst von Brand [EMAIL PROTECTED] wrote:
Nikita Danilov [EMAIL PROTECTED] wrote:
It's other way around: declaration is guarded by the preprocessor
conditional so that nobody accidentally use
Hans Reiser [EMAIL PROTECTED] wrote:
Nick Piggin wrote:
Hans Reiser wrote:
So why is the code in the kernel so hard to read then?
Linux kernel code is getting better, and Andrew Morton's code is
especially good, but for the most part it's unnecessarily hard to
read. Look at the
Hello
Clemens Eisserer wrote:
Hello again,
I am currently re-installing my linux system and I would like to use
reiser4 since I think its really powerful and great (and is well
written too ;) ).
However, will it be possible to convert a non-compressed reiser4
partition to a compressed
Vladimir V. Saveliev wrote:
Hello
Clemens Eisserer wrote:
Hello again,
I am currently re-installing my linux system and I would like to use
reiser4 since I think its really powerful and great (and is well
written too ;) ).
However, will it be possible to convert a non-compressed reiser4
Nick Piggin wrote:
[snip devfs]
Yeah I was just trying to introduce some humour to the thread!
Or maybe deflate one flamewar by starting another :)
;-)
Jens Axboe wrote:
Seeing as you are the one that is apparently bothered by the misnomer,
it follows that you would be the one submitting a patch for this. Not
that it would be accepted though, I don't see much point in renaming
functions and breaking drivers just because of a slightly bad name.
David Masover wrote:
And personally, if it was my FS, I'd stop working on fsck after it was
able to check. That's what it's for. To fix an FS, you wipe it and
restore from backups.
Umm, this is going too far David. Our fsck should work, and we will
give his script to Vitaly to play with
Horst von Brand wrote:
Nikita Danilov [EMAIL PROTECTED] wrote:
It is supposed to go into the kernel, which is not exactly warning-free.
While I have no passionate feelings about Nikita's ifdef, I must note
that Reiser4 will always be warning free within 3 days of my finding out
that
Nikita Danilov wrote:
Lorenzo Allegrucci [EMAIL PROTECTED] writes:
[...]
Why not just rename the kernel option elevator to iosched ?
At least update Documentation/kernel-parameters.txt to be consistent,
but I think kernel boot options are considered to be a part of the user
space API
Thanks much for this test script, Vitaly, please give it a try and tell
me how it goes.
Hans
Pavel Machek wrote:
Hi!
V3 is obsoleted by V4 in every way. V3 is old code that should be
marked as deprecated as soon as V4 has passed mass testing. V4 is far
superior in its coding style also.
Horst von Brand wrote:
Funny that the texbook algorithms aren't used in real life. Wonder why...
Try BSD. If the BSD book can be believed, they usetexbook algorithms.
;-)
On Sep 20, 2005, Stephen Pollei [EMAIL PROTECTED] wrote:
On 9/19/05, Horst von Brand [EMAIL PROTECTED] wrote:
Nikita Danilov [EMAIL PROTECTED] wrote:
It's other way around: declaration is guarded by the preprocessor
conditional so that nobody accidentally use znode_is_loaded() outside of
Horst von Brand wrote:
Could you /please/ stop your snide remarks on the code and its authors? If
for nothing else, the very people you are insulting in public are the exact
ones that will decide if they take on the work of auditing and integrating
your code.
Our code was called messy. It
On Tue, Sep 20, 2005 at 09:41:36AM -0500, David Masover wrote:
And personally, if it was my FS, I'd stop working on fsck after it was
able to check. That's what it's for. To fix an FS, you wipe it and
restore from backups.
If that's Reiser4's philosophy, just make sure you tell all of your
On Tue, Sep 20 2005, Hans Reiser wrote:
Jens Axboe wrote:
Seeing as you are the one that is apparently bothered by the misnomer,
it follows that you would be the one submitting a patch for this. Not
that it would be accepted though, I don't see much point in renaming
functions and
David Masover [EMAIL PROTECTED] wrote:
Pavel Machek wrote:
V3 is obsoleted by V4 in every way. V3 is old code that should be
marked as deprecated as soon as V4 has passed mass testing. V4 is far
superior in its coding style also. Having V3 in and V4 out is at this
point just stupid.
On Tue, 2005-09-20 at 13:57 -0400, Theodore Ts'o wrote:
On Tue, Sep 20, 2005 at 09:41:36AM -0500, David Masover wrote:
And personally, if it was my FS, I'd stop working on fsck after it was
able to check. That's what it's for. To fix an FS, you wipe it and
restore from backups.
If
On Tue, Sep 20 2005, Hans Reiser wrote:
Horst von Brand wrote:
Funny that the texbook algorithms aren't used in real life. Wonder why...
Try BSD. If the BSD book can be believed, they usetexbook algorithms.
Even the BSD people are looking for better algorithms. To be honest, I
Hans Reiser writes:
Horst von Brand wrote:
Funny that the texbook algorithms aren't used in real life. Wonder why...
Try BSD. If the BSD book can be believed, they usetexbook algorithms.
The textbook one-way elevator (as indeed exemplified by FreeBSD's
Hans Reiser [EMAIL PROTECTED] wrote:
Horst von Brand wrote:
[...]
It is supposed to go into the kernel, which is not exactly warning-free.
While I have no passionate feelings about Nikita's ifdef, I must note
that Reiser4 will always be warning free within 3 days of my finding out
that
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hello,
In kernel 2.6.14-rc1-mm1, Reiser4 present 2 regressions with regard to
2.6.13-mm1 :
A) Suspend-to-disk does not work because the process [ent:hda8] can't be
stopped.
$ mount | grep hda8
/dev/hda8 on /home/laurent/kernel type reiser4
Hello everyone.
Any comments are welcome.
David, would you please review the following:
KEY MANAGEMENT IN REISER4
I suggest to consider The KRS (Kernel Key Retention Service, (c) Red
Hat) for
keeping/accessing the keys. The KRS includes a number of syscalls and kernel
So yes, hmm sad that there is not compress-option - it could be easily
doable with the files in the pseudo directory of every single file.
This way one could select which files to compress and which not -
however thats not that important for me. I am just happy that there is
at least one serious
Dnia Tue, 20 Sep 2005 21:27:42 +0200, David Masover [EMAIL PROTECTED] napisał:
Laurent Riffard wrote:
A) Suspend-to-disk does not work because the process [ent:hda8] can't be
stopped.
Strange, this used to work. Haven't had occasion to try it again
lately, though.
B) Can't mount a loop
Clemens Eisserer schrieb:
So yes, hmm sad that there is not compress-option - it could be easily
doable with the files in the pseudo directory of every single file.
This way one could select which files to compress and which not -
however thats not that important for me. I am just happy that
Tomasz Chmielewski wrote:
Clemens Eisserer schrieb:
So yes, hmm sad that there is not compress-option - it could be easily
doable with the files in the pseudo directory of every single file.
This way one could select which files to compress and which not -
however thats not that important for
Hello.
Вторник 20 сентября 2005 11:51 | Pavel Machek:
Can V4 survive few hours of test below?
Maybe I'm doing something wrong here, but ext2 have failed on second check
of first pass with
Second check...
e2fsck 1.34 (25-Jul-2003)
Pass 1: Checking inodes, blocks, and sizes
Pass 2: Checking
_
Коммерциализация интеллектуальной собственности.
Документальное оформление,оценка,коммерческое использование
и управление интеллектуальной собственностью в качестве имущества предприятия
On Tue, 20 Sep 2005 23:28:12 +0400, Roman I Khimov said:
--nextPart1692600.LIfSYN1P7A
Maybe I'm doing something wrong here, but ext2 have failed on second check
of first pass with
Second check...
e2fsck 1.34 (25-Jul-2003)
Pass 1: Checking inodes, blocks, and sizes
Pass 2: Checking
Forgive me if this has been answered recently, but I haven't gotten my
last two dozen e-mails for today yet.
Regarding the compression plugin, what sort of compression can one
expect from it? I know that compression of files like bz2 will vary (in
that they'll be essentially uncompressed) from
On Tue, Sep 20, 2005 at 12:18:46PM -0600, Jonathan Briggs wrote:
I use Reiser3 and Reiser4 on all my systems and fsck has always worked
even if it has been much slower than I would like. The only problems
I've experienced have been on the same level as when an ext2/3
filesystem fsck dumps
On Tue, Sep 20, 2005 at 04:15:41PM -0400, [EMAIL PROTECTED] wrote:
On Tue, 20 Sep 2005 23:28:12 +0400, Roman I Khimov said:
--nextPart1692600.LIfSYN1P7A
Maybe I'm doing something wrong here, but ext2 have failed on second check
of first pass with
Second check...
e2fsck 1.34
Clay Barnes wrote:
Also: Is the algorithm set in stone? If so what is it? If not, what
is it now/expected to be?
Probably lzo, which is already used for other things like network
connections (ssh, openvpn, and so on). The nice thing about lzo is that
it's fast, faster than gzip or bzip2,
On Tue, 20 Sep 2005 17:17:13 EDT, Theodore Ts'o said:
An exit code of 1 means that filesystem errors were corrected
(successfully).
Right. The problem is that this was a *second* check, after the first one
terminated with exit code 0, 1, or 2. Thus, it *should* have exited with 0.
The
Hi!
Can V4 survive few hours of test below?
Maybe I'm doing something wrong here, but ext2 have failed on second check
of first pass with
No, you have probably just found bug in e2fsck...
Second check...
e2fsck 1.34 (25-Jul-2003)
I have 1.38 here, so yours is too old.
OTOH if reiser4
Hi,
recent threads on compression made me think about the algorithms.
Will there be just one compression algorithm for everything,
or many and ways to choose from them?
Will it be possible to, say, write plugins of your own to do
the compression?
Which algorithms are considered for compression?
Hello.
Среда 21 сентября 2005 01:37 | Pavel Machek:
Second check...
e2fsck 1.34 (25-Jul-2003)
I have 1.38 here, so yours is too old.
I'll compile something new tomorrow and try to retest it.
OTOH if reiser4 survives that for 80 cycles... that's pretty good.
Actually 125 before I've
On 9/20/05, Clay Barnes [EMAIL PROTECTED] wrote:
Forgive me if this has been answered recently, but I haven't gotten my
last two dozen e-mails for today yet.
Regarding the compression plugin, what sort of compression can one
expect from it?
[snip]
Just a general, no reiser4 specifc answer
On 9/20/05, Hans Reiser [EMAIL PROTECTED] wrote:
Horst von Brand wrote:
Nikita Danilov [EMAIL PROTECTED] wrote:
It is supposed to go into the kernel, which is not exactly warning-free.
Is that what this thread boils down to, that you guys think the compile
should fail not warn?
I don't care
Hi!
Second check...
e2fsck 1.34 (25-Jul-2003)
I have 1.38 here, so yours is too old.
I'll compile something new tomorrow and try to retest it.
OTOH if reiser4 survives that for 80 cycles... that's pretty good.
Actually 125 before I've got completely tired of HDD noise. :)
On 9/20/05, David Masover [EMAIL PROTECTED] wrote:
Probably lzo, which is already used for other things like network
connections (ssh, openvpn, and so on). The nice thing about lzo is that
it's fast, faster than gzip or bzip2, and gets decent compression -- not
great, but decent. I don't
On 9/20/05, Stephen Pollei [EMAIL PROTECTED] wrote:
On 9/20/05, Hans Reiser [EMAIL PROTECTED] wrote:
Horst von Brand wrote:
Nikita Danilov [EMAIL PROTECTED] wrote:
It is supposed to go into the kernel, which is not exactly warning-free.
Is that what this thread boils down to, that you
On 9/20/05, Alexandre Oliva [EMAIL PROTECTED] wrote:
On Sep 20, 2005, Stephen Pollei [EMAIL PROTECTED] wrote:
On 9/19/05, Horst von Brand [EMAIL PROTECTED] wrote:
Since when has a missing declaration prevented anyone calling a function in
C?!
Never AFAIK... KR, ANSI,ISO C89, c99,
On Tue, 20 Sep 2005, James Lamanna wrote:
On 9/20/05, Stephen Pollei [EMAIL PROTECTED] wrote:
On 9/20/05, Hans Reiser [EMAIL PROTECTED] wrote:
Horst von Brand wrote:
Nikita Danilov [EMAIL PROTECTED] wrote:
It is supposed to go into the kernel, which is not exactly warning-free.
Is
On 9/20/05, Vadim Lobanov [EMAIL PROTECTED] wrote:
On Tue, 20 Sep 2005, James Lamanna wrote:
On 9/20/05, Stephen Pollei [EMAIL PROTECTED] wrote:
On 9/20/05, Hans Reiser [EMAIL PROTECTED] wrote:
Horst von Brand wrote:
Nikita Danilov [EMAIL PROTECTED] wrote:
What about #warning /
On Tue, Sep 20, 2005 at 09:51:33AM +0200, Pavel Machek wrote:
Do you have working fsck for V4? Until then, you should not claim that
users should switch. Journalling does not help you, if you have
unexpected kernel problem or hardware trouble, fsck _is_ mandatory.
Can V4 survive few hours of
Theodore Ts'o wrote:
On Tue, Sep 20, 2005 at 12:18:46PM -0600, Jonathan Briggs wrote:
I use Reiser3 and Reiser4 on all my systems and fsck has always worked
even if it has been much slower than I would like. The only problems
I've experienced have been on the same level as when an ext2/3
Thanks Ted, I'll ask Vitaly to read the paper, and tell us what he
thinks should be learned from it for V4.
Hans
Theodore Ts'o wrote:
On Tue, Sep 20, 2005 at 09:51:33AM +0200, Pavel Machek wrote:
Do you have working fsck for V4? Until then, you should not claim that
users should switch.
Stephen Pollei wrote:
Also note my opinion, doesn't really count if you grep the kernel
sources for pollei, you won't find anything.
Your opinion counts, but lets see what Nikita says before I say
anything. Nikita is more expert than I in regards to compiler tricks.
Pavel Machek wrote:
Hi!
Second check...
e2fsck 1.34 (25-Jul-2003)
I have 1.38 here, so yours is too old.
I'll compile something new tomorrow and try to retest it.
OTOH if reiser4 survives that for 80 cycles... that's pretty good.
Actually 125 before I've got
Theodore Ts'o wrote:
Another interesting refinement would be to analyze the resulting
filesystem after it has been repaired to determine how much data could
be salvaged by the fsck program.
We use reiserfs3 to store data and have had very good luck in getting
data off of real world, hard
Ric Wheeler wrote:
As an earlier thread on lkml showed this summer, we still have a long
way to go to getting consistent error semantics in face of media
failures between the various file systems. I am not sure that we even
have consensus on what that default behavior should be between
On 9/20/05, Theodore Ts'o [EMAIL PROTECTED] wrote:
The script could be improved by select random locations to damage the
filesystem, instead of hard-coding the seek=7 value. Seek=7 is good
for testing ext2/ext3 filesystems, but it may not be ideal for other
filesystems.
What would be
Hans Reiser wrote:
Ric Wheeler wrote:
As an earlier thread on lkml showed this summer, we still have a long
way to go to getting consistent error semantics in face of media
failures between the various file systems. I am not sure that we even
have consensus on what that default behavior
Gregory Maxwell wrote:
On 9/20/05, Theodore Ts'o [EMAIL PROTECTED] wrote:
There is a very interesting paper that I coincidentally just came
across today that talks about making filesystems robust against
various different forms of failures of modern disk systems. It is
going to be presented
So the post about file system failure modes made me think of something
interesting...
We'd discussed in the past that it would be interesting to store
cryptographic hashes of files as metadata for facilitating
applications which require hashes as well as data integrity. Of
course, the challenge
On 9/20/05, Gregory Maxwell [EMAIL PROTECTED] wrote:
An interesting idea: select the algo and a range of compression
levels per file, but select the actual compression level at flush time
based on some estimate of how loaded the system is.. :)
Probably not worth it even though the amount of
Laurent Riffard wrote:
Hello,
In kernel 2.6.14-rc1-mm1, Reiser4 present 2 regressions with regard to
2.6.13-mm1 :
A) Suspend-to-disk does not work because the process [ent:hda8]
can't be stopped.
$ mount | grep hda8
/dev/hda8 on /home/laurent/kernel type reiser4 (rw,nosuid,nodev)
Ric Wheeler wrote:
Hans Reiser wrote:
Ric Wheeler wrote:
As an earlier thread on lkml showed this summer, we still have a long
way to go to getting consistent error semantics in face of media
failures between the various file systems. I am not sure that we even
have consensus on what
I have been thinking about it for quite a while, and while I would be
interested in seeing if it was still needed after the elevator code gets
fixed to not congest, it should go in until then.
Hans
All,
I've compiled a new version of the 2.6.9-11.EL kernel for reiser 4
support. I applied the reiser4 patch, and rebuilt the kernel with it as
a module. I've installed the resultant kernel, and everything seems
fine with it, in general. I downloaded and compiled the reiser tools -
reiser4 is a completely different filesystem. reiserfsprogs will not
work. Use reiser4progs from ftp://ftp.namesys.com/pub/reiser4progs/.
You'll need to install libaal first.
You shouldn't be using insmod. Use modprobe instead. A clean rebuild of
your kernel might fix the symbol error.
On Tue,
On 9/20/05, Hans Reiser [EMAIL PROTECTED] wrote:
I am not a big fan of formal committees, but would be happy to take
part in any effort to standardize, code and test the result...
The committee could simply exchange a set of emails, and agree on
things. I doubt it needs to get all
78 matches
Mail list logo
