<?xml version="1.0" encoding="utf-8"?>
<rss xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:foaf="http://xmlns.com/foaf/0.1/" xmlns:og="http://ogp.me/ns#" xmlns:rdfs="http://www.w3.org/2000/01/rdf-schema#" xmlns:schema="http://schema.org/" xmlns:sioc="http://rdfs.org/sioc/ns#" xmlns:sioct="http://rdfs.org/sioc/types#" xmlns:skos="http://www.w3.org/2004/02/skos/core#" xmlns:xsd="http://www.w3.org/2001/XMLSchema#" version="2.0" xml:base="https://www.linuxjournal.com/tag/glusterfs">
  <channel>
    <title>GlusterFS</title>
    <link>https://www.linuxjournal.com/tag/glusterfs</link>
    <description/>
    <language>en</language>
    
    <item>
  <title>Two Pi R</title>
  <link>https://www.linuxjournal.com/content/two-pi-r</link>
  <description>  &lt;div data-history-node-id="1211672" class="layout layout--onecol"&gt;
    &lt;div class="layout__region layout__region--content"&gt;
      
            &lt;div class="field field--name-field-node-image field--type-image field--label-hidden field--item"&gt;  &lt;img src="https://www.linuxjournal.com/sites/default/files/nodeimage/story/200px-Raspberry_Pi_Logo.png" width="200" height="253" alt="" typeof="foaf:Image" class="img-responsive" /&gt;&lt;/div&gt;
      
            &lt;div class="field field--name-node-author field--type-ds field--label-hidden field--item"&gt;by &lt;a title="View user profile." href="https://www.linuxjournal.com/users/kyle-rankin" lang="" about="https://www.linuxjournal.com/users/kyle-rankin" typeof="schema:Person" property="schema:name" datatype="" xml:lang=""&gt;Kyle Rankin&lt;/a&gt;&lt;/div&gt;
      
            &lt;div class="field field--name-body field--type-text-with-summary field--label-hidden field--item"&gt;&lt;p&gt;
Although many people are excited about the hardware-hacking possibilities
with the Raspberry Pi, one of the things that interests me most is
the fact that it is essentially a small low-power Linux server I can
use to replace other Linux servers I already have around the house. In
previous columns, I've talked about using the Raspberry Pi to replace
the server that controls my beer fridge and colocating a Raspberry Pi in
Austria. After I colocated a Raspberry Pi in Austria, I started thinking
about the advantages and disadvantages of using something with so many
single points of failure as a server I relied on, so I started thinking
about ways to handle that single point of failure. When you see "Two Pi
R", you probably think the R stands for the radius for a circle. To me, it
stands for redundancy. I came to the conclusion that although one Pi isn't
redundant, two Pi are.
&lt;/p&gt;

&lt;p&gt;
So, in this article, I'm building the foundation for setting up redundant
services with a pair of Raspberry Pis. I start with setting up a
basic clustered network filesystem using GlusterFS. In later articles,
I'll follow up with how to take advantage of this shared storage to set
up other redundant services. Of course, although I'm using a Raspberry Pi
for this article, these same steps should work with other hardware as well.
&lt;/p&gt;

&lt;h3&gt;
Configure the Raspberry Pis&lt;/h3&gt;

&lt;p&gt;
To begin, I got two SD cards and loaded them with the latest version
of the default Raspberry Pi distribution from the official Raspberry Pi
downloads page, the Debian-based Raspbian. I followed the documentation
to set up the image and then booted in to both Raspberry Pis while
they were connected to a TV to make sure that the OS booted and that
SSH was set to start by default (it should be). You probably also will 
want to use the raspi-config tool to expand the root partition to fill
the SD card, since you will want all that extra space for your redundant
storage. After I confirmed I could access the Raspberry Pis remotely,
I moved them away from the TV and over to a switch and rebooted them
without a display connected.
&lt;/p&gt;

&lt;p&gt;
By default, Raspbian will get its network information via DHCP; however,
if you want to set up redundant services, you will want your Raspberry
Pis to keep the same IP every time they boot. In my case, I updated my
DHCP server so that it handed out the same IP to my Raspberry Pis every
time they booted, but you also could edit the /etc/network/interfaces
file on your Raspberry Pi and change:

&lt;/p&gt;&lt;pre&gt;&lt;code&gt;
iface eth0 inet dhcp
&lt;/code&gt;&lt;/pre&gt;


&lt;p&gt;
to:

&lt;/p&gt;&lt;/div&gt;
      
            &lt;div class="field field--name-node-link field--type-ds field--label-hidden field--item"&gt;  &lt;a href="https://www.linuxjournal.com/content/two-pi-r" hreflang="und"&gt;Go to Full Article&lt;/a&gt;
&lt;/div&gt;
      
    &lt;/div&gt;
  &lt;/div&gt;

</description>
  <pubDate>Tue, 17 Dec 2013 20:19:23 +0000</pubDate>
    <dc:creator>Kyle Rankin</dc:creator>
    <guid isPermaLink="false">1211672 at https://www.linuxjournal.com</guid>
    </item>
<item>
  <title>Special Report: Scale Out with GlusterFS</title>
  <link>https://www.linuxjournal.com/content/special-report-scale-out-glusterfs</link>
  <description>  &lt;div data-history-node-id="1174990" class="layout layout--onecol"&gt;
    &lt;div class="layout__region layout__region--content"&gt;
      
            &lt;div class="field field--name-field-node-image field--type-image field--label-hidden field--item"&gt;  &lt;img src="https://www.linuxjournal.com/sites/default/files/nodeimage/story/glusterfs.jpeg" width="302" height="340" alt="" typeof="foaf:Image" class="img-responsive" /&gt;&lt;/div&gt;
      
            &lt;div class="field field--name-node-author field--type-ds field--label-hidden field--item"&gt;by &lt;a title="View user profile." href="https://www.linuxjournal.com/user/800005" lang="" about="https://www.linuxjournal.com/user/800005" typeof="schema:Person" property="schema:name" datatype="" xml:lang=""&gt;LJ Staff&lt;/a&gt;&lt;/div&gt;
      
            &lt;div class="field field--name-body field--type-text-with-summary field--label-hidden field--item"&gt;&lt;img src="http://www.linuxjournal.com/files/linuxjournal.com/ufiles/imagecache/medium-350px-centered/u1002061/glustercover.jpeg" alt="" title="" class="imagecache-medium-350px-centered" /&gt;&lt;p&gt;
Learn how to install, benchmark and optimize this popular, shared-nothing and scalable open-source distributed filesystem in this special 12 page report.
&lt;/p&gt;
&lt;p&gt;
Please provide your email below for an instant download.&lt;/p&gt;

&lt;?php $block = module_invoke('webform', 'block', 'view', 'block-webform-client-block-1174878');
print $block['content'];
??&gt;&lt;/div&gt;
      
            &lt;div class="field field--name-node-link field--type-ds field--label-hidden field--item"&gt;  &lt;a href="https://www.linuxjournal.com/content/special-report-scale-out-glusterfs" hreflang="und"&gt;Go to Full Article&lt;/a&gt;
&lt;/div&gt;
      
    &lt;/div&gt;
  &lt;/div&gt;

</description>
  <pubDate>Tue, 05 Nov 2013 17:57:08 +0000</pubDate>
    <dc:creator>LJ Staff</dc:creator>
    <guid isPermaLink="false">1174990 at https://www.linuxjournal.com</guid>
    </item>

  </channel>
</rss>
