Differences between version 9 and predecessor to the previous major change of Ext3.
Other diffs: Previous Revision, Previous Author, or view the Annotated Edit History
| Newer page: | version 9 | Last edited on Thursday, February 24, 2005 6:44:30 am | by AristotlePagaltzis | Revert |
| Older page: | version 8 | Last edited on Wednesday, February 23, 2005 2:21:50 pm | by BrettNash | Revert |
@@ -17,10 +17,11 @@
<pre>
tune2fs -o acl /dev/''partition''
</pre>
-Remember to change fstab(5) to mount the partition as [Ext3], and then unmount/remount it or reboot. (You do not have to do this immediately). Do not
mount an [Ext3] partition as type [Ext2], unless
you are sure
the journal is
empty. Otherwise you
may have a
-filesystem
due to incomplete journal operations or that when
it is mounted
as ext3
the kernel
will happily commit journal options
to your modified filesytem
.
+Remember to change fstab(5) to mount the partition as [Ext3], and then unmount/remount it or reboot. (You do not have to do this immediately).
+
+You can always
mount an [Ext3] partition as type [Ext2] —
you just will not have any journalling performed. However, __beware__: if
the journal was not
empty before doing so, your FileSystem
may be
corrupted. This may happen either right away
due to incomplete journal operations or once you mount
it as [Ext3] again because
the [Kernel]
will then
happily commit old operations
to your now
modified FileSystem
. So make sure the [Ext3] FileSystem was properly flushed and unmounted before you attempt to mount it as [Ext2]. (AddToMe: is this sufficient to ensure integrity?)
You can also enabled hashed directories with a 2.6 [Kernel]. This speeds up lookups for directories that contain a large numbers of files/directories.
<pre>
