Slackware (12.2/13) as a High Availability NAS Server
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.
Slackware (12.2/13) as a High Availability NAS Server
I'm about to put together a new NAS solution here, and wanted to get some feedback on the choices/potential pitfalls.
I intend to run two servers in a high availability configuration using drbd & heartbeat on slackware 12.2 (or 13 depending on when it arrives). I personally have no experience with drbd or heartbeat yet, but the research says it's the only way to go.
The data will be stored on a mixture of Seagate and Western Digital 1TB disks, all hooked up through a 3ware 12-lane 9650SE-12ML. Initially there'll be 4x1TB disks in RAID6 with a fifth as a hot spare in each server. And there'll be a RAID1 on velociRaptors for the OS. The data will then be accessed via NFS and Samba from a number of different client OSes. It will be a big mixture of office stuff, source code, large binaries, and massive amounts of simulation data and silicon chip layouts.
Obviously I'm thinking about the Slackware-specific issues here. I have run Slack on a supermicro board like this one will be before and am happy with the configuration of NAS/Samba for the layout, but haven't ever run slack with drbd, heartbeat or 3ware raid. Also, I'm looking at getting an APC UPS each for the servers, but again, I haven't run Powerchute with slackware before for graceful shutdown in the event of prolonged outage.
Anything to comment?
Last edited by zordrak; 07-02-2009 at 07:21 AM.
Reason: Addition of UPS
I did a small fraction of what your planning with 2 Slack boxes using RAID0 and NBD as hosts for KVM guests. Each box has a single 1TB HD and they are connected with CAT5 through a D-Link 1GB switch. In my case both boxes are on a single APC UPS, no Powerchute, but with as many drives as you're supporting a UPS for each box is probably a better fit. DRDB was something I considered but was more than I wanted to tackle at the time. Powerchute is not something I'm familiar with but sounds like I should be.
I'll be interested in following your project. Good luck and keep us up to date!.
The idea of having two UPSes isn't actually so that I can have one for each box - both will serve both boxes. Each server has 3 PSUs, two will be plugged in to one UPS, the third into the other one. This way, if one of the UPSes fail, both machines will remain available.
Distribution: slackware 13.1,13.37,14.0,14.1,14.2 64 and 32bit and arm
regarding the apc part. You don't need powerchute. You can build a slack apcupsd package (get the slackbuild from slackbuilds.org or use sbopkg)
once you have done the manual changes as noted in the readme and set the daemon running, you can easily check the ups state by doing something like
As you will have each machine running on both ups's it makes it more complicated deciding what to do if one ups switches of or fails, and the other is still ok, but in the same status file is an indication of the running time available which at least gives you some more info to work with.
The defaults are to shutdown when there is only 3 minutes, or 5% of battery power left. you'll want to do your own thing here, as machine co-operation is essential.
Unless you have a dedicated crossover link between the two machines, running your network switch on dual power supplies and ups's will also be essential so that the two servers can co-operate. - have fun.!
As for heartbeat: I have no experience with it so I can't offer any help.
As for DRDB: I prefer AoE because it scales better and is simpler to set up (not that DRDB is hard hehe).
With DRDB you either have an active/passive 2 node setup or an active/active setup (you'll need a cluster FS for this. I used OCFS2 and liked it a lot).
You are also "limited" to a RAID1.
This is fine in most situations.
With AoE (plus software raid) you can use whatever you want
You can have a 1 active node + "n" passives, or even "n" active nodes (again, need cluster FS for more than 1 active).
You can build a network RAID1 with 1+"n" disks (DRDB only lets you do 1+1) or even a RAID6 with 100 disks!
The only limit is your hardware (number of disks, NICs and switches).
Note: the AoE initiator is a kernel module, so Slackware already has this. All you need to do is compile the AoE target binary (I used vblade)
Get it here: http://aoetools.sourceforge.net/