Single file version available here.
Last updated on 2008-06-28.
To discuss, comment here.
| Prev | Next | |
| Home |
Posted by: Linegod on Aug 30, 2001
http://www.warpedsystems.sk.ca/modules.php?op=modload&name=News&file=article&sid=324
After reading various articles on the virtues of different Journalled Files Systems, I decided to take the plunge and convert my test box over to ext3. Armed with the latest Mandrake kernel and e2fsprogs I set out to bring my drives into the 21st Century :)
The process itself could not have been simpler, and as the title of the article suggest, was done with the following 4 steps:
That's all there was to it. The reason for unmounting 'not in use' file systems is that it will hide the '.journal' entry after creation, where on mounted filesystems it will be visable.
To 'shock test' the system (not recommended), I simply cut the power to the box and watch it boot up. All but the '/' file system, which still ran fsck, came back up without a hitch. I believe the '/' problem is due to the new 'devfsd', but will do some tests to confirm this.
If you are looking for a quick and easy solution for journalled file systems, I'd say ext3 is the way to go.
> did u manage to mount it data=writeback? wouldn't work for me....but should > be a lot faster.
Haven't tried that yet, but I will…..
No luck here either. Must tinker some more….
pasnak
From: http://www.redhat.com/support/wpapers/redhat/ext3/tuning.html#elevator
The /sbin/elvtune program can be used to trade off between throughput and latency. For example, you might run: /sbin/elvtune -r 1024 -w 2048 /dev/sdd to change the elevator settings for the device /dev/sdd (including all the partitions on /dev/sdd). Changes to the elevator settings for a partition will apply to the elevator for the device the partition is on; all partitions on a device share the same elevator.
Once you have found elvtune settings that give you your most satisfactory mix of latency and throughput for your application set, you can add the calls to the /sbin/elvtune program to the end of your /etc/rc.d/rc.local script so that they are set again to your chosen values at every boot.
There are some characteristic loads that show very significant speed improvement with the data=writeback option. In those cases, the data consistency guarantees are essentially the same as the ext2 file system; the difference is that the file system integrity is maintained continuously during normal operation.
If you switch from ext2 to ext3 and find that your application performance drops substantially, the data=writeback option is likely to give you a significant amount of performance back; you will still have some of the availability benefits of ext3 (file system is always consistent) even if you do not have the more expensive data consistency guarantees.
Tong
| Prev | Next | |
| Home |