On Sunday 14 September 2003 14:46, you wrote:

fsanta wrote:

...

Hi I was reading your FAQ but didn't understand this:

'Full data journaling is considered by many to be a good way to achieve file data integrity across system crashes.'

Does this mean that I don't lose my files when the system crashes or does 'file data integrity' have a deeper meaning? I'm considering going Reiser for our lan which is currently ext3 with SuSE 8.2

Thanks. Steve.

metadata journaling ensures that you don't need to run fsck after a crash. data journaling ensures that even if there is a crash during a write, all of the data pointed to is data that was written to the file. data journaling offers performance advantages in v3 for workloads with lots of fsyncs, and performance disadvantages for other workloads.

V4 performs fully atomic writes, that is, a write either occurs in its entirety, or it does not. data journaling (for any fs) does not guarantee this. v4 does this without significant performance cost due to its architecture (actually v4 is much higher performance than v3). v4 however is beta code.

Hi Hans and thanks for your time. We are a small international school with a 21 node Linux only network via NIS under SuSE 8.2. Our server, a PIV with 1024 RAM and ide disk seems to be more and more crippled the as /home grows. We use KDE on all clients and the server disk is around 90% full most of the time. Would Reiser help with this? Or do you think our hardware is inadequate for the task. Thanks, Steve.