journaling fs a good idea?

Printable View

06-06-2003, 01:27 AM
stefan_isaacs

journaling fs a good idea?

hi,

i'm finally running knoppix 3.2 on my Sony laptop (with a hard disk install) and
while everything is working great am thinking about going to a journaling fs (ext3
or reiser?).

So the question is, since I'm barely familiar with the journaling concept, these fs
types are more resistant to "crash-damage" than a normal ext2 fs, right?

If so, should I prefer one over the other (ext3 or reiser)? What are the trade-offs
over ext2 (if any) and over one another?

thanks,
Stefan
06-06-2003, 01:50 AM
rickenbacherus

Phooey on ext2- it's a waste of your time. There is really no reason to use it (well ok I use it on my /boot partition) but that's it. Definitely go with ext3 or reiser. Personally I use nothing but reiser. Yes journaling is better WAY better. Just google for it you'll find plenty of reasons to use it.
07-27-2003, 03:14 AM
Forse

Check this out

U really should check this out http://forums.goldenrain.net/viewtopic.php?t=9
07-27-2003, 01:30 PM
Edwin

Re: Check this out

Quote:

Originally Posted by Forse

U really should check this out http://forums.goldenrain.net/viewtopic.php?t=9

Assuming you are the author of that post, could you clarify two points on ReiserFS?

Quote:

ReiserFS doesn't perform well with big files >500mb. ReiserFS is mature and most suited for database files.

Those two statements seem incompatibel to me. Database files easily exceed 500 MB. The files I work with anyway.

Quote:

If u need quota then go with ext3 since reiserFS support is sucky...and is not mature yet

What is (or are) quota?

TIA

- - Edwin
07-27-2003, 05:16 PM
Forse

Quote:

Originally Posted by Linux docs

Quota allows you to specify limits on two aspects of disk storage: the number of inodes a user or a group of users may possess; and the number of disk blocks that may be allocated to a user or a group of users.

The idea behind quota is that users are forced to stay under their disk consumption limit, taking away their ability to consume unlimited disk space on a system. Quota is handled on a per user, per file system basis. If there is more than one file system which a user is expected to create files, then quota must be set for each file system separately.

About database...well I can be wrong...But we have an enterprise server with MySQL DB. It contails a lot of small files. I guess it depends what u do with DB. Usually forums generate a lot of small files.

ReiserFS was designed for a small files so performance with big files is not so good. ReiserFS4 will change that.

BtW. That forum is mine and I just opened :) So if u want u could post there...and I garantee an answer :wink:
07-27-2003, 07:12 PM
Stephen

Re: Check this out

Quote:

Originally Posted by Edwin

Those two statements seem incompatibel to me. Database files easily exceed 500 MB. The files I work with anyway.

That is the total of the files in the database you are refering too not one big > 500mb file I think this is where the confusion is.

Quote:

What is (or are) quota?

TIA

- - Edwin

Quota limits the amount of HD space a user can have for their use.
07-27-2003, 10:03 PM
Edwin

Re: Check this out

Quote:

Originally Posted by Stephen

That is the total of the files in the database you are refering too not one big > 500mb file I think this is where the confusion is.

Well, actually I was not. My Db creates 3 files per table. If one has to store lots of text (or graphics) tables can grow quickly on you. Even more so if one has to store historical data. Denormalizing to speed up queries grows them even faster. Besides that there are DBMS's that store everthing (catalogue, index and data) all in one big file.

But I googled on ReiserFS. Guess I have some more reading to do. Fascinating stuff.

Regards,

- - Edwin
07-28-2003, 01:03 AM
Stephen

Re: Check this out

Quote:

Originally Posted by Edwin

Well, actually I was not. My Db creates 3 files per table. If one has to store lots of text (or graphics) tables can grow quickly on you. Even more so if one has to store historical data. Denormalizing to speed up queries grows them even faster. Besides that there are DBMS's that store everthing (catalogue, index and data) all in one big file.

But I googled on ReiserFS. Guess I have some more reading to do. Fascinating stuff.

Regards,

- - Edwin

I stand corrected it's been over 10 years since I last played with any database and even then a 500mb HD was a dream let alone using it for one file, must be a real PIA if the database gets corrupted with only a couple files in it. I guess I'd have some reading to do myself if I ever wanted to use one again.
07-29-2003, 01:33 AM
Edwin

Re: Check this out

Quote:

Originally Posted by Stephen

and even then a 500mb HD was a dream let alone using it for one file, must be a real PIA if the database gets corrupted with only a couple files in it. I guess I'd have some reading to do myself if I ever wanted to use one again.

If you ever come upon a DBMS that stores everthing in one file, don't do any reading. Just run as fast as you can and don't forget to close and lock the door. If these babies get corrupted (and they will) you will suffer much, much, very much more than a PIA.

I leave that to your own imagination.

Regards,

- - Edwin