SlackwareThis Forum is for the discussion of Slackware Linux.
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Introduction to Linux - A Hands on Guide
This guide was created as an overview of the Linux Operating System, geared toward new users as an exploration tour and getting started guide, with exercises at the end of each chapter.
For more advanced trainees it can be a desktop reference, and a collection of the base knowledge needed to proceed with system and network administration. This book contains many real life examples derived from the author's experience as a Linux system and network administrator, trainer and consultant. They hope these examples will help you to get a better understanding of the Linux system and that you feel encouraged to try out things on your own.
Click Here to receive this Complete Guide absolutely free.
Just out of curiosity are you using Ext4 with journaling? I've been reading up on SSD's and pretty much got all the info I need, but there seems to be debate about the benefits (if any) of disabling journaling. Some say its faster without, others say there is no difference.
I don't use journaling, there is really no point. Journaling is in place to help recover from read/write errors, but since a SSD can't get bad sectors or any of the other ailments of traditional HDDs, it has little effect. An SSD will still go bad, but when it does it will be a catastrophic type of failure, and require the drive to be replaced immediately, at which point you just recover from backups. In other words, a journal is not going to help you when an SSD finally bites the dust. You could still have problems with a hard shutdown, but nothing fsck can't fix if it ever happens.
The drive is also mounted with noatime and nodiratime options, which greatly reduce filesystem overhead. In actuality, these two options will save you more repeated writes and general overhead than disabling journaling anyway.
I have a mushkin 60G Callisto deluxe in my 64b desktop with ext4. I was using a wd raptor before and didn't notice much difference. They really start to shine when running 2-3 in raid-0 but Linux still puts some stuff on only one drive till the kernel is loaded I think. I think in a laptop it would be a bigger difference.
ext4 with journaling here. When you get a drive, you should get a quality drive that should work for a long time regardless the filesystem. Of course, you should learn a bit about how SSDs work, and pick the right filesystem options for your applications.
OCZ Vertex 40GB with reiserfs. Runs like a rocket on my htpc. Why reiserfs? Dont know, I have been using reiser since 2004 and did not even think about which fs I was gonna use on this ssd drive when I formatted it...
it is really an immense performance increase if used properly.
What do you mean by "if used properly"? Is there some settings, tweaks or improvements to implement to get the max out of it?