Posted: Sat Jun 22, 2002 2:25 am Post subject: The right filesystem for the right files???

i have noticed a lot of people claiming that a certain file system is better for this or that. for instance i have read that people consider reiserfs the best for small files but some dont really trust it for this root filesystem.....and XFS is better for larger files...and ext3 is just all around good..

anyone have any good comments about this? about which filesystem is best for what and why that is so?...

also, has anyone experimented with using multiple file systems for certian system directories? for instance:

/usr/portage should be the FS with the fastest small file access speed because the portage system has so many small files...

and /usr/src/ should be similar because of the many many files in the kernel source,

but /home could be XFS or ext3 because people download larger items(multiple megabyte) often..

gimme your thoughts and your preferences on this...

right now i run the following:
/home is XFS
/usr is ReaserFS
/boot is ext3
i have a suse install on another partition:
/suse (hda3) is ext3 becuase suse8 prefered it and i wasn't willing to argue

ext3 is stable (AFAIK) but slow compared to every other journaling file system; xfs as well as jfs didn't work with my kernel config (xfs lost data, jfs usage resulted in kernel panics) I'm happy with reiserfs now. using it on every machine (regardless of the distro used) since well over two years without problems, just gave the others a try after installing gentoo.
the problems may well arise out of uncommon kernel configurations, that are nevertheless needed to get all hardware to work with high-memory support and the preemption-patch enabled

I have used ReiserFS, ext3, and XFS on gentoo and for all purposes I like XFS but unfortunately it causes the kernel to have somewhat more bulk (200Kb+) and doesn't function properly with preempt enabled (usually).

ReiserFS has been good to me so far, is light on the kernel, and is fast for most things.

Ext3 is slow, I have had corruption (gentoo recue disk saves the day), and once I lost my journal for no apparent reason.

Note: When I talk about bulk, it isn't because of ram but because my kernel needs to fit on a bootdisk along with syslinux. I'm sure some will disagree with what I said and that is ok, one was just giving output on ones experience with journaling filesystems._________________This message self destructed a long time ago.

Ask six different linux users what file types you should use and you'll get six different answers. A lot of it is very subjective and dependent on your particular needs. (i.e. speed vs. stability vs. simplicity)

Try them all out -- see which one floats your boat the best.

--kurt_________________The problem with political jokes is that they get elected

I would say no. I use ext3 for all my stuff. I've tried reiser and XFS, but I always come back to ext3 simply because it's easier and I don't notice all that big of a speed difference.

Now, after I post this, about 419 other people are going to post about how XFS made their this much faster and reiserfs made their system that much faster, so again, it's all a very subjective thing that depends on your particular needs.

--kurt_________________The problem with political jokes is that they get elected

im most interested in which file system to put which type of files on. i know fat32 and ext2 are horribly slow for putting mp3s on. as in it take longer to ls a directory or find a file on them. and im also interested in improving response time of the file system for certain tasks,

i can feel a noticable difference when using ext2 or 3. in fact a google search showed my that ext2 and 3 have to noticable performance difference as ext3 is just ext2 with a journal. but i dont feel that this is a problem for some directories like /boot....which doesnt need to be blazing fast as it just has a couple config files and the kernel... but my /usr/portage directory needs to be faster so that emerge doesnt take so dang long to write files to..

why is their not a good database file system?? is it possible to mount a database as a directory?

so a search would just look in the database index which is very small and searches would be REALLY fast, small file access can be amazingly fast in some SQL benchmarks..

how about something like
/boot is a real ext3 partition
/root is a real reiserfs partition
but /lib /home /usr are all just a mounted database?

how good is the support for the BFS(be file system)? which is a fairly fast databased file system, of cource a file system tools package would need included because most of the file services in beos were managed by tracker...

I would say no. I use ext3 for all my stuff. I've tried reiser and XFS, but I always come back to ext3 simply because it's easier and I don't notice all that big of a speed difference.

Now, after I post this, about 419 other people are going to post about how XFS made their this much faster and reiserfs made their system that much faster, so again, it's all a very subjective thing that depends on your particular needs.

--kurt

I was mainly just curious. I'm using ext3 and don't expect to change (if for no other
reason than I'm lazy). I'm more concerned with stability than a second or two faster response time._________________You're jumping to conclusions, so I can't keep up with you. Go on without me, I'll just slow you down.

I don't think anyone was disputing benchmarks, but rather it didn't "feel" faster.
What you do with the fs is probably the most important factor._________________You're jumping to conclusions, so I can't keep up with you. Go on without me, I'll just slow you down.

Those using ext3 (I use XFS) they can enhance the fs performance by telling it to journal only metadata and not the data itself (as XFS and reiser do it).

The default option is to journal both which is safer but hurts performance. You can refer to LinuxToday article describing ext3. Check the speed section._________________There's someone in my head but it's not me - Pink Floyd

One mode, data=writeback, limits the data integrity guarantees, allowing old data to show up in files after a crash, for a potential increase in speed under some circumstances. (This mode, which is the default journaling mode for most journaling file systems, essentially provides the more limited data integrity guarantees of the ext2 file system and merely avoids the long file system check at boot time.)

_________________There's someone in my head but it's not me - Pink Floyd