Differences between current version and revision by previous author of FileSystem.
Other diffs: Previous Major Revision, Previous Revision, or view the Annotated Edit History
| Newer page: | version 28 | Last edited on Saturday, February 13, 2010 12:39:43 pm | by JohnBillings | |
| Older page: | version 25 | Last edited on Monday, May 15, 2006 12:53:44 pm | by PerryLorier | Revert |
@@ -11,9 +11,9 @@
Linux has full read/write support for [FAT32], full read support for [NTFS], and limited write support. If you wish to format a file system so that Windows and Linux can both see it, choose FAT32.
!! Traditional Linux file systems
-In contrast, the traditional FileSystem of choice on Linux is [Ext2]. It is very trusty and rock solid - losing much data from an [Ext2] partition is nearly impossible short of a hardware failure. The only problem is that an fsck takes a very long time. On servers that don't get rebooted in months, this is not much of a headache, but Linux is making its way to the desktop, where machines get rebooted frequently. Therefore, a variant that supports journalling was created: [Ext3].
+In contrast, the traditional FileSystem of choice on Linux is [Ext2]. It is very trusty and rock solid - losing much data from an [Ext2] partition is nearly impossible short of a hardware failure. The only problem is that an fsck takes a very long time. On servers that don't get rebooted in months, this is not much of a headache, but Linux is making its way to the desktop, where machines get rebooted frequently. Therefore, a variant that supports journalling was created: [Ext3]. The next revision of this filesystem, [Ext4] is gaining wider acceptance and aims to increase performance when dealing with large files
.
!! Journalling file systems
Journalling file systems keep a log of changes pending completion, so in the event of a crash, they can quickly finish up or undo changes as required to bring the FileSystem back to a consistent state. A full consistency check with fsck crawling the entire disk is then unnecessary. Nevertheless, you should fsck partitions at least every once in a blue moon to ensure that no inconsistencies creep in. The likelihood is low, but better to be safe than sorry.
