None I can think of, I do this with mine. I slice out root, var, var/log, usr, and home to lvm's, usually adding another dump slice under /mnt for "everything else" including vm images and such across the whole disk. I do not however provision all the vg space, reserving it for another slice, lvextending, etc case I run out of space elsewhere.I am looking at a new Linux laptop, and I have the option of a mSata SSD drive or a conventional drive. I am considering a 1 TB Samsung 840 EVO mSata SSD for the OS and all my partitions.
1. Are there any reasons not to use a SSD for the full disk, as opposed to just for the OS? Other than saving money, as a small SSD would cost a lot less!
You'll want to do the optimizations still. I have a pretty complex setup I have to build at an initrd usually outside of installers, aligning blocks/chunks across disparate filesystems from mdraid, cryptsetup, lvm, to ext4. I don't use trim (cryptsetup vulnerabilities), but it's possible to do full-stack traversal like that apparently.
2. I have seen recommendations on the net to backup the drive to a spinning drive. The laptop has a couple of bays, so I could put a back up drive in one of the bays. Does this make sense, or have SSDs matured enough that they will last like a spinning drive?
Yes, they die. Often in my experience. I never NOT raid1 them now. My first I thought it'd be cool to raid0, and holy crap it was fast. Then one (thus all my data) died after 2 months. Raid1 ftw from here out. I have way too much proprietary data to not keep it resilient (mdadm), keep it secure (cryptsetup), and keep it flexible (lvm).
3. Anything else I should be aware of when moving to the world of SSDs?
Thanks,
Mark
--------------------------------------------------- PLUG-discuss mailing list - PLUG-discuss@lists.phxlinux.org To subscribe, unsubscribe, or to change your mail settings: http://lists.phxlinux.org/mailman/listinfo/plug-discuss