harde schijf formateren

[Gast]

wat is het verschil tussen het formateren in reiserfs en ext3

en welke kan ik het beste gebruiken

 

[-= [ Appien ] =-]

ReiserFS :

 

Three reasons why ReiserFS is great for you:

 

ReiserFS has fast journaling, which means that you don't spend your life waiting for fsck every time your laptop battery dies, or the UPS for your mission critical server gets its batteries disconnected accidentally by the UPS company's service crew, or your kernel was not as ready for prime time as you hoped, or the silly thing decides you mounted it too many times today.

 

ReiserFS is based on fast balanced trees. Balanced trees are more robust in their performance, and are a more sophisticated algorithmic foundation for a filesystem. When we started our project, there was a consensus in the industry that balanced trees were too slow for filesystem usage patterns. We proved that if you just do them right they are better. We have fewer worst case performance scenarios than other filesystems and generally better overall performance. If you put 100,000 files in one directory, we think its fine; many other filesystems try to tell you that you are wrong to want to do it.

 

ReiserFS is more space efficient. If you write 100 byte files, we pack many of them into one block. Other filesystems put each of them into their own block. We don't have fixed space allocation for inodes. That saves 6% of your disk.

 

Ok, it's time to fess up. The interesting stuff is still in the future. Because they are nifty, we are going to add database and hypertext like features into the filesystem. Only by using balanced trees, with their effective handling of small files (database small fields, hypertext keywords), as our technical foundation can we hope to do this. That was our real motivation. As for performance, we may already be slightly better than the traditional filesystems (and substantially better than the journaling ones). But they have been tweaking for decades, while we have just got started. This means that over the next few years we are going to improve faster than they are.

 

Speaking more technically:

 

ReiserFS is a filesystem using a plug-in based object oriented variant on classical balanced tree algorithms. The results when compared to the ext2fs conventional block allocation based filesystem, running under the same operating system and employing the same buffering code, suggest that these algorithms are overall more efficient and every passing month are becoming yet more so. Loosely speaking, every month we find another performance cranny that needs work; we fix it. And every month we find some way of improving our overall general usage performance.

 

The improvement in small file space and time performance suggests that we may now revisit a common OS design assumption that one should aggregate small objects using layers above the filesystem layer. Being more effective at small files does not make us less effective for other files. This is truly a general purpose FS. Our overall traditional FS usage performance is high enough to establish that. ReiserFS has a commitment to opening up the FS design to contributions; we are now adding plug-ins so that you can create your own types of directories and files.

 

 

Meer info

 

 

 

EXT3 :

 

The ext3 filesystem is a journaling extension to the standard ext2 filesystem on Linux. Journaling results in massively reduced time spent recovering a filesystem after a crash, and is therefore in high demand in environments where high availability is important, not only to improve recovery times on single machines but also to allow a crashed machine's filesystem to be recovered on another machine when we have a cluster of nodes with a shared disk.

 

 

This talk will describe the ext3 filesystem, both its design goals and its implementation. It will explain some of the challenges involved in adding journaling in a way which is completely compatible with existing ext2 filesystems (it is possible to migrate existing ext2 filesystems to ext3 and back again), and will cover the architecture of the implementation, which involves a completely new, generic block device journaling layer in the kernel.

 

Meer info

 

 

En tja, welke beter is durf ik zo geen oordeel over te geven.

[Gast]

maakt voor de werking dus niets uit

 

of ik films opneem of data van de pc opsla