Salam smua,
Sejak kenal linux, saya menconfigur pc/laptop kepada dual boot, windows dan ubuntu(of course). Untuk itu saya akan pecahkan harddisk kepada 3 partition.
1- NTFS untuk windows
2- Ext3 untuk Linux
3- Fat32 untuk data agar kedua-dua OS boleh baca dan tulis ke partition ini.
Sebenarnya saya kurang selesa dengan partition ke tiga kerana Fat32 tidak memberikan kawalan capaian data seperti yg terdapat pada NTFS dan ext3. Tetapi kerana tiada pilihan, terpaksa dikekalkan begitu.
Tetapi kini dengan adanya Ext2IFS saya boleh membaca/tulis ke Ext3 dari OS windows(seronoknya). Cuma walaupun ianya boleh baca ext3, namun ia tidak support journaling.
"The Ext3 file system is the Ext2 file system which has been extended by journaling. Ext3 is backward-compatible to Ext2 - an Ext3 volume can be mounted and used as an Ext2 volume. Just as older Linux Kernels which do not know the Ext3 file system can mount Ext3 volumes (as Ext2 volumes), the Ext2 file system driver ext2fs.sys for Windows incorporated in this software package can do it without any problems, too. Of course you do not take advantage of the journaling of the Ext3 file system if you mount it as an Ext2 file system.
If you mount an Ext3 file system as an Ext2 file system and the file system is not cleanly dismounted, (e.g. due to a system crash), you have to run the e2fsck tool. (Linux does it automatically.) Running e2fsck can take several hours on large volumes. You do not benefit from journaling the Ext3 file system, because you have to run e2fsck.
If you mount an Ext3 file system as an Ext3 file system (journaling) and the file system is not cleanly dismounted due to a system crash, things are much better: When the volume is mounted next time as an Ext3 file system, a replay of the journal will be done, after which the file system will be consistent. You need not run e2fsck. (If you run e2fsck nevertheless, it won’t find any errors of the Ext3 file system, because there will not be any errors after replaying the journal.)
If a volume is mounted as Ext3 file system, any new data is first completely written into the journal, and then into the file system. This is also called a transaction. Finally, the data is removed from the journal. So a journal only contains data when you are writing to the file system. After a clean dismount of the Ext3 file system, the journal is empty.
When the Linux kernel mounts an Ext3 file system, it first checks whether the journal contains complete transactions (not written yet due to a prior crash). If there are any, it does the already mentioned replay of the journal, which means that all data of the journal is written to the file system, and any data will be removed from it. So a replay always repairs any damage caused by a prior crash.
With the described way of writing the journal and the file system’s data and with a replay of the journal after a crash, consistency of the file system is always achieved. Thus, e2fsck will not find any error.
The Ext2 file system driver of the Ext2 IFS software will refuse mounting an Ext3 file system which contains data in its journal, just like older Linux kernels which have no Ext3 support. In this way data loss and damaging the file system is avoided when the journal is subsequently replayed. So you can access only those Ext3 volumes with the Ext2 IFS software which have been cleanly dismounted beforehand."
oh ya hampir terlupa nak beri url 
http://www.fs-driver.org/index.html
ok, selamat mencuba….
written by cperdana
Recent Comments