<html xmlns:v="urn:schemas-microsoft-com:vml" xmlns:o="urn:schemas-microsoft-com:office:office" xmlns:w="urn:schemas-microsoft-com:office:word" xmlns:m="http://schemas.microsoft.com/office/2004/12/omml" xmlns="http://www.w3.org/TR/REC-html40">
<head>
<meta http-equiv=Content-Type content="text/html; charset=us-ascii">
<meta name=Generator content="Microsoft Word 12 (filtered medium)">
<style>
<!--
/* Font Definitions */
@font-face
{font-family:"Cambria Math";
panose-1:2 4 5 3 5 4 6 3 2 4;}
@font-face
{font-family:Calibri;
panose-1:2 15 5 2 2 2 4 3 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
{margin:0cm;
margin-bottom:.0001pt;
font-size:11.0pt;
font-family:"Calibri","sans-serif";}
a:link, span.MsoHyperlink
{mso-style-priority:99;
color:blue;
text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
{mso-style-priority:99;
color:purple;
text-decoration:underline;}
span.EmailStyle17
{mso-style-type:personal-compose;
font-family:"Calibri","sans-serif";
color:windowtext;}
.MsoChpDefault
{mso-style-type:export-only;}
@page Section1
{size:612.0pt 792.0pt;
margin:72.0pt 72.0pt 72.0pt 72.0pt;}
div.Section1
{page:Section1;}
-->
</style>
<!--[if gte mso 9]><xml>
<o:shapedefaults v:ext="edit" spidmax="1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext="edit">
<o:idmap v:ext="edit" data="1" />
</o:shapelayout></xml><![endif]-->
</head>
<body lang=EN-GB link=blue vlink=purple>
<div class=Section1>
<p class=MsoNormal>Morning guys,<o:p></o:p></p>
<p class=MsoNormal><o:p> </o:p></p>
<p class=MsoNormal>We’re currently working with Voyage 5x which seems to
work quite nicely for us, however I can see some upcoming benefits of us using
the new 6x release and I wanted to try and clear up a few questions about the
new file system which is implemented on the new release.<o:p></o:p></p>
<p class=MsoNormal><o:p> </o:p></p>
<p class=MsoNormal>In our application for Voyage we use MySQL to collect data,
this is then written to the disk and must remain there after a reboot. At the
moment we’ve always taken care of this by using the WIKI document found
here <a href="http://wiki.voyage.hk/dokuwiki/doku.php?id=remove_ro">http://wiki.voyage.hk/dokuwiki/doku.php?id=remove_ro</a>
which is an anything but ideal situation but has always worked well for us.<o:p></o:p></p>
<p class=MsoNormal><o:p> </o:p></p>
<p class=MsoNormal>Now, I assume that with this new move to AUFS it’s
about time we started doing things properly. At the moment I understand next to
nothing about AUFS and how it works but I’m hoping we’ll be able to
configure it for our needs.<o:p></o:p></p>
<p class=MsoNormal><o:p> </o:p></p>
<p class=MsoNormal>If you guys had data you needed to persist on the disk regardless
of a reboot or power loss how would you go about it? I know we’ve talked
in the past about having a secondary scratch partition on the disk which we
use, is this still our best option? Or does AUFS give us some better
configuration options to set some space aside on the same partition as the OS?<o:p></o:p></p>
<p class=MsoNormal><o:p> </o:p></p>
<p class=MsoNormal>Aside from the MySQL database which we need to persist I
also have a bunch of log files and some XML configuration files generated by
our application which we need to keep permanently, other than that most changes
can be lost.<o:p></o:p></p>
<p class=MsoNormal><o:p> </o:p></p>
<p class=MsoNormal>I’m looking for a solution which is easy to implement
and also simple to replicate so we can duplicate the cards quickly.<o:p></o:p></p>
<p class=MsoNormal><o:p> </o:p></p>
<p class=MsoNormal>Many thanks guys, I appreciate any pointers.<o:p></o:p></p>
<p class=MsoNormal><o:p> </o:p></p>
<p class=MsoNormal>Robert<o:p></o:p></p>
</div>
</body>
</html>