I assume you plan on putting the whole openSuse install on the SSD? If not,
LMK. First thing I will tell you is don't do that.
OK: have some tips for you after scrounging around the openSuse notes (and
Ubuntu, but most of the Ubuntu treatment does not apply). Take a look at my
drive(s):
LABEL=root / ext4 noatime,discard,acl,user_xattr 1 1
My root partition is on the SSD. Add attributes "noatime" and "discard".
LABEL=var /var ext4 acl,user_xattr 1 2
Assign /var to a rotating HD, where atime is OK and many
writes/erasures is no problem. Your goal is to avoid the write erasure
cycles and you do not want /var on your SSD. Can you format this to another
drive?
/dev/disk/by-id/ata-OCZ-VERTEX3_OCZ-7UOH6807P2VF8I1K-part1 swap
swap defaults 0 0
Swap, above, is normal, but on the SSD. If there is an SSD mod for
swap, I do not know of it.
/dev/disk/by-id/ata-OCZ-VERTEX3_OCZ-7UOH6807P2VF8I1K-part3 /home
ext4 noatime,discard,acl,user_xattr 1 2
Note the addition of noatime and "discard" again on the home partition,
again on the SSD.
Now, the cool part. Only on openSuse, to my knowledge, and I do not
understand yet why, once you set the attributes like I mentioned, it will
automatically make many TMPFS sections for you. These exist somewhere
between DRAM and the SSD (another thing I do not understand completely and
hope some Linux whiz will comment on--maybe we can all build a (open
source!) SSD how-to for the Suse people to post.) Ubuntu people and early
SSD users of openSuse were promted to manually create a TMPFS (a temp file
system completely in RAM), but it is done automatically here in 12.1.
I have 6 automatically created file systems, each of which doubled when I
doubled RAM in my system. I have 16 gigs on my desktop. This is what I found
in the partitioner when I was done installing:
7.84 GB TmpFS /dev/shm
7.84 GB TmpFS /run
7.84 GB TmpFS /sys/fs/cgroup
7.84 GB TmpFS /media
7.84 GB TmpFS /var/lock
7.84 GB TmpFS /var run
This autoformatting surprized me and I hope someone can tell me what
triggered this. Either it's kernel support of SSD drives or something Suse
is doing. Really cool.
I sure as hell didn't do all this! And this system screams. However, on
every boot, it will "hang" while configuring these temp file systems for
about 15 seconds, right as you reach KDE's desktop. This reduces your start
time to what a 10k hard disk or raid system might boot in. But with any
other function after reaching KDE it flat out screams.
Every once in a while you want to run:
fstrim -v /
to "trim" the drive. I assume you know about the Trim support.
The less I do it, the faster it seems to go, so I am getting lazier about
it. Try once a week or so at first.
Comments welcomed to anyone with different experiences.