Hi, I would like to hear some comments on how to set up my new server with Slackware.

I got some new hardware and I plan to set it up as follows:

A SSD 120GB drive, on this set up the / partition and other partitions
2 new 500 GB HDD drives where I plan to put my /home partition on a RAID 1 array.

I will use this machine for my company where I will have my users an ERP software running,
and an asterisk server.

Any suggestions on which files systems to use and how to best partition the drives ?
Should I set up LVM on the SSD ?

Any comments are very welcome, the processor is an AMD FX-8320 X8 (3.5 GHZ) socket AM3+ with
16GB of ram and an Asrock 980DE/U3S3 motherboard.

You should have spent bit more money and bought an ASUS mainboard instead of the cheaper Asrock board.

Nice buy on that unit. Good specs for much lower cash-point.

Regarding load-out, I recommend ext4 partitions on anything huge and, typically, I use ext2 on the smaller /var and /tmp partitions I set up to trap logs, etc. Then again, if your asterisk system uses mysql you'll want the /var to be huge if you left the mysql DBs on the stock setup location.

Not being particularly versed with asterisk, I'd have to shy away from too much that is that app-specific.

Which ERP solution are you running? Given that it + asterisk = probably your most mission-critical segments, it may help shed some light on the other 1/2 of that puzzle.

Oh, one more tidbit, I shelled out for a high performance double-fan massive heat-sync non-oem cooling solution for my AMD solutions. It's a known issue that they tend to massively underspec their cooling. It's one of the reasons they've earned a bit of a bad name.

Don`t forget to enable trim on that ssd.

i think the ssd will not last long if you let /var on it.. limited write cycles.

i would put /var on a hdd..

Hi,
Not an issue on newer SSD. My suggestion to the OP would be to make sure to setup TRIM as suggested. Look at this: http://www.linuxquestions.org/questi...ml#post4586044 The whole thread has some useful information. Plus, be sure not to mix settings for Older SSD with new SSD setups. More so for newer setups being used for older SSD. Some people still parrot old setup issues with newer SSD. Not so for new controllers or cell type.

I have another machine with an ASUS MB but I have to say that its not playing nicely, this is the reason why I had gone with Asrock.

I will not use mysql with asterisk, but have to use it with the ERP (www.dolibarr.org), which runs on php and mysql.
Is there any reason on to use ext2 , I have used mostly xfs, but have not much experience with ext4, and what about puting btrfs on SSD ?

ERP is Dolibarr.

[/QUOTE]
Ok, thanks for that tip, I will see if I can find a good cooler or a better fan.

I forgot to mention that my ssd is a Samsung 840 EVO.

---------- Post added 10-27-13 at 01:29 PM ----------

@onebuck, thanks for the link.

how do i know i have a newer not an older? are there special prints on it?
i trust hdd still a bit more and would non the less be carefule.

@Stuferus, I would say that a newer SSD would be the one bought in this last year. SSD's are out already few years and therefore I know there were issues with them before. On some of the newer ones the manufacutrers give a warranty of many million writes iirc.

Ok, so I will put on my ssd the following dirs / /usr and on my HDD on a RAID 1 /home /var /tmp , what do you think ?

that sounds like a solid idea.

the dbs are going to grow so I'd definitely think the HDD is better for them.

depending on how your system is going to allocate and free db data remember to look into shrinking since most dbs these days are empty space if not shrunk regularly. I do it as party of my backup so it stays a small operation.

also note that Slackware is doing away with mysql in favor of the maria engine but it's a drop in replacement so shouldn't cause you many issues if any.

In this case the only benefit you will have from the SSD is faster boot time, so if you don't care about that just don't use a SSD.

saxa, the new Samsung SSD have a pretty long cycle of read/write
and if your db size is less than 16 GB, it doesnt matter where you have your DB on.
is however your DB bigger than 16GB, it is a huge win to put it on the SSD disk.

we have customers running purely on SSD disks, and there are no issues (and those disks are 3 years old now)
they use ext4 on the SSD disks. (raid 10)

your initial setup plan is good to use the HDD in raid 1 on your /home and the SSD on the rest.
do make sure that your DB makes backups to /home (as this is your safety net) or to another server