Book Review: Managing RAID on Linux
Title: Managing RAID on LinuxAuthor: Derek VadalaPublisher: O'Reilly & AssociatesISBN: 1-56592-730-3Price: $39.95 US, $61.95 CAN
Almost every Linux system administrator probably is familiar with the concept of RAID (redundant array of independent disks), but most probably aren't too confident about setting one up on their own. Many may have muddled through the process by using minimal documents (that is, howtos and single chapters in general Linux books) or vendor specific documentation. In such situations, one can only hope for the best when arbitrarily choosing a RAID type and configuring it. Recently, though, O'Reilly has published a unique book called, Managing RAID on Linux, which focuses on RAID and related topics.
A RAID typically, by definition, involves redundant hard drives linked together by special hardware or software. "Using RAID has two basic advantages: redundancy, or the ability to survive a disk failure, and increased performance. Depending on which RAID level you choose, you get varying degrees of each of these features", writes Vadala. A RAID also can be used to link hard drives together to create a virtually larger hard drive that is seamless to the operating system and to the users. Some RAID can improve hard disk storage and retrieval speeds by breaking data up into blocks that are written to or retrieved from several drives simultaneously. Some RAIDS, however, cause a reduction in hard disk performance due to the redundancy, which is why it's important to understand hardware configuration with RAID. These possible gains make RAID an inviting feature to implement on busy servers.
Managing RAID on Linux is not very long by computer book standards--about 250 pages. There are only seven chapters, but most are quite hefty and in depth. The first chapter is brief, only ten pages, and it defines many RAID terms. If you're a system administrator, you might try getting your manager to read at least this first chapter, so you can talk the same language when the discussing hardware purchases necessary to build a hard drive array.
A manager who wants to understand more also might read the second chapter. It covers planning a RAID and goes a little deeper into the different types of RAIDs. Vadala provides some excellent straightforward examples of situations in which each RAID would be useful. There's also a section that illustrates the impact hardware makes on a RAID. Performance and dependability of a redundant hard drive system is greatly affected by hardware. I'm not necessarily referring to hardware-based RAID controllers but to types of hard drives, hard drive controllers, PCI bus rating of motherboards and so on. Vadala helps clarify several aspects of hardware related to RAID performance.
The third and fourth chapters of Managing RAID on Linux deal with the process of constructing a software-based RAID. Vadala says, "There has been a long standing stigma against software RAID. However, software RAID on Linux performs exceptionally and it's reliable. It's comparable to using a decent hardware controller, and better-performing in some cases." In his book, he goes into reconfiguring the Linux kernel for a RAID. This is something most Linux fans cringe at the thought of attempting, but Vadala walks the reader through the process fairly painlessly. He then spells out how to create partitions and format drives for each RAID type. In the fourth chapter Vadala elaborates a little more on kernel options; he likes to hold back at times so as not to overwhelm the reader. As a result, you may want to read the entire book before jumping into installing a RAID on a production server. You may also want to experiment first with an old workstation and some spare parts, too.
Vadala's fifth chapter is dedicated to hardware RAIDs. He covers six popular types of RAID controllers that are offered by five different vendors. These hardware RAIDs are configured and administered by proprietary software. Vadala gives the reader some things to consider when purchasing a hardware RAID. And, he describes aspects of configuring a hardware RAID that are common to all of them. He then covers the details of each vendor RAID.
An aspect of RAIDs that is often overlooked is the value of an appropriate filesystem. In Vadala's sixth chapter he says that for larger, heavily used servers that have either extremely large files or thousands of smaller files, one should consider using a journaling filesystem, such as ext3 or ReiserFS. In this chapter he expounds on the merits of each of these and a few others.
|Speed Up Your Web Site with Varnish||Jun 19, 2013|
|Non-Linux FOSS: libnotify, OS X Style||Jun 18, 2013|
|Containers—Not Virtual Machines—Are the Future Cloud||Jun 17, 2013|
|Lock-Free Multi-Producer Multi-Consumer Queue on Ring Buffer||Jun 12, 2013|
|Weechat, Irssi's Little Brother||Jun 11, 2013|
|One Tail Just Isn't Enough||Jun 07, 2013|
- Speed Up Your Web Site with Varnish
- Containers—Not Virtual Machines—Are the Future Cloud
- Non-Linux FOSS: libnotify, OS X Style
- Lock-Free Multi-Producer Multi-Consumer Queue on Ring Buffer
- Linux Systems Administrator
- Senior Perl Developer
- Technical Support Rep
- UX Designer
- Android's Limits
- Weechat, Irssi's Little Brother
Free Webinar: Hadoop
How to Build an Optimal Hadoop Cluster to Store and Maintain Unlimited Amounts of Data Using Microservers
Realizing the promise of Apache® Hadoop® requires the effective deployment of compute, memory, storage and networking to achieve optimal results. With its flexibility and multitude of options, it is easy to over or under provision the server infrastructure, resulting in poor performance and high TCO. Join us for an in depth, technical discussion with industry experts from leading Hadoop and server companies who will provide insights into the key considerations for designing and deploying an optimal Hadoop cluster.
Some of key questions to be discussed are:
- What is the “typical” Hadoop cluster and what should be installed on the different machine types?
- Why should you consider the typical workload patterns when making your hardware decisions?
- Are all microservers created equal for Hadoop deployments?
- How do I plan for expansion if I require more compute, memory, storage or networking?