<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:Wingdings;
panose-1:5 0 0 0 0 0 0 0 0 0;}
@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;}
@font-face
{font-family:Tahoma;
panose-1:2 11 6 4 3 5 4 4 2 4;}
@font-face
{font-family:Consolas;
panose-1:2 11 6 9 2 2 4 3 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
{margin:0cm;
margin-bottom:.0001pt;
font-size:12.0pt;
font-family:"Times New Roman","serif";
color:black;}
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;}
pre
{mso-style-priority:99;
mso-style-link:"HTML Preformatted Char";
margin:0cm;
margin-bottom:.0001pt;
font-size:10.0pt;
font-family:"Courier New";
color:black;}
span.HTMLPreformattedChar
{mso-style-name:"HTML Preformatted Char";
mso-style-priority:99;
mso-style-link:"HTML Preformatted";
font-family:Consolas;
color:black;}
span.EmailStyle19
{mso-style-type:personal-reply;
font-family:"Calibri","sans-serif";
color:#1F497D;}
.MsoChpDefault
{mso-style-type:export-only;
font-size:10.0pt;}
@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 bgcolor=white lang=EN-GB link=blue vlink=purple>
<div class=Section1>
<p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";
color:#1F497D'>Hi Chris,<o:p></o:p></span></p>
<p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";
color:#1F497D'><o:p> </o:p></span></p>
<p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";
color:#1F497D'>OK, Well hopefully with two brains on the job we’ll be
able to solve the issue. </span><span style='font-size:11.0pt;font-family:Wingdings;
color:#1F497D'>J</span><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";
color:#1F497D'><o:p></o:p></span></p>
<p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";
color:#1F497D'><o:p> </o:p></span></p>
<p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";
color:#1F497D'>I’m very new to the idea of a ro file system, it’s
something we’d never worked with before until coming to voyage and even
then we disabled it from the get-go to save problems like this arising.
However, it’s something we’re now keen to solve as it’s
caused us problems with duplication having them in RW.<o:p></o:p></span></p>
<p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";
color:#1F497D'><o:p> </o:p></span></p>
<p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";
color:#1F497D'>My knowledge on the RO system was that the applications could ‘write’
data to the fs but that it was properly written to the disk and thus lots after
a reboot? Is that not correct? From what you’re saying it sounds as nothing
can be written to the disk when in RO mode, how do things like syslog work in
this situation? Surely they’re writing to something?<o:p></o:p></span></p>
<p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";
color:#1F497D'><o:p> </o:p></span></p>
<p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";
color:#1F497D'>Thanks,<o:p></o:p></span></p>
<p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";
color:#1F497D'><o:p> </o:p></span></p>
<p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";
color:#1F497D'>Robert<o:p></o:p></span></p>
<p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";
color:#1F497D'><o:p> </o:p></span></p>
<div>
<div style='border:none;border-top:solid #B5C4DF 1.0pt;padding:3.0pt 0cm 0cm 0cm'>
<p class=MsoNormal><b><span lang=EN-US style='font-size:10.0pt;font-family:
"Tahoma","sans-serif";color:windowtext'>From:</span></b><span lang=EN-US
style='font-size:10.0pt;font-family:"Tahoma","sans-serif";color:windowtext'>
Chris [mailto:csrodley@xnet.co.nz] <br>
<b>Sent:</b> 08 May 2009 00:16<br>
<b>To:</b> Robert Rawlins - Think Blue<br>
<b>Cc:</b> voyage-linux@voyage.hk<br>
<b>Subject:</b> Re: [Voyage-linux] MySQL<o:p></o:p></span></p>
</div>
</div>
<p class=MsoNormal><o:p> </o:p></p>
<p class=MsoNormal>Hi Robert,<br>
<br>
Sorry, I have been away all week.<br>
We have found that after apt-getting mysql and without even setting it up,
voyage is not able to remountro on boot up after mysql has been started.<br>
There has been a number of power cuts over the past few days and we have lost 2
systems as a result. <br>
We have other units not running mysql that work find after a powercut because
they are read-only.<br>
<br>
I assume that there is some sort of temp file that need to be put into tmpfs or
something. We have switched off all logs on mysql conf, so that should not be
the problem.<br>
<br>
In this system - on reboot everything is transferred off the network back onto
the computer, so there is no need for database files to persist across reboots.<br>
<br>
I guess what I really need to know is what mysql is doing to take control of
the filesystem so it can't be remounted read only.<br>
<br>
Thanks for the help!<br>
Chris<br>
<br>
<br>
Robert Rawlins - Think Blue wrote: <o:p></o:p></p>
<pre>Gustin, thanks for the advice!<o:p></o:p></pre><pre><o:p> </o:p></pre><pre>I'll likely be DDing the entire disk so at least that won't be too much of a challenge. Things generally seem pretty simple here then, that's good to know.<o:p></o:p></pre><pre><o:p> </o:p></pre><pre>I'll try this out later today and see how I get on, I'll once I've got it up and running I'll look into the MySQL configuration to see what needs to be changed in respect to that to get things working.<o:p></o:p></pre><pre><o:p> </o:p></pre><pre>I'd be interested to hear from Chris (the original poster) about the problems he had with MySQL, even in read only I'd expect the server to be able to write files, they'd just be lost after a reboot? Correct?<o:p></o:p></pre><pre><o:p> </o:p></pre><pre>Thanks again,<o:p></o:p></pre><pre><o:p> </o:p></pre><pre>Robert<o:p></o:p></pre><pre><o:p> </o:p></pre><pre>-----Original Message-----<o:p></o:p></pre><pre>From: Gustin Johnson [<a
href="mailto:gustin@echostar.ca">mailto:gustin@echostar.ca</a>] <o:p></o:p></pre><pre>Sent: 07 May 2009 12:09<o:p></o:p></pre><pre>To: Robert Rawlins - Think Blue<o:p></o:p></pre><pre>Cc: <a
href="mailto:voyage-linux@voyage.hk">voyage-linux@voyage.hk</a><o:p></o:p></pre><pre>Subject: Re: [Voyage-linux] MySQL<o:p></o:p></pre><pre><o:p> </o:p></pre><pre>-----BEGIN PGP SIGNED MESSAGE-----<o:p></o:p></pre><pre>Hash: SHA1<o:p></o:p></pre><pre><o:p> </o:p></pre><pre>Robert Rawlins - Think Blue wrote:<o:p></o:p></pre><pre> <o:p></o:p></pre>
<blockquote style='margin-top:5.0pt;margin-bottom:5.0pt'><pre>Hi Rainer,<o:p></o:p></pre><pre><o:p> </o:p></pre><pre>This is something we have talked about in the past but I have not tried to<o:p></o:p></pre><pre>do it yet. I've never worked with multiple partitions in Linux before. I<o:p></o:p></pre><pre>like this idea very much.<o:p></o:p></pre><pre><o:p> </o:p></pre><pre> <o:p></o:p></pre></blockquote>
<pre>This is nothing new. There is a lot of documentation out there.<o:p></o:p></pre><pre>Basically, you create the partition, then format it, then add an entry<o:p></o:p></pre><pre>in /etc/fstab so that it is mounted on boot.<o:p></o:p></pre><pre><o:p> </o:p></pre><pre> <o:p></o:p></pre>
<blockquote style='margin-top:5.0pt;margin-bottom:5.0pt'><pre>Do you have any advice on how to create this second partition? And how I can<o:p></o:p></pre><pre> <o:p></o:p></pre></blockquote>
<pre><o:p> </o:p></pre><pre>I use cfdisk, but my main environment is Linux. You may wish to RTFM<o:p></o:p></pre><pre>partitioning under Linux. It is easy to turf an existing partition<o:p></o:p></pre><pre>regardless of the OS you are using.<o:p></o:p></pre><pre><o:p> </o:p></pre><pre> <o:p></o:p></pre>
<blockquote style='margin-top:5.0pt;margin-bottom:5.0pt'><pre>write files to it? Are there any gotchas I need to watch out for? We're<o:p></o:p></pre><pre> <o:p></o:p></pre></blockquote>
<pre><o:p> </o:p></pre><pre>Once mounted, the new partition appears as another folder on your file<o:p></o:p></pre><pre>system. You write files to it like you would any other folder.<o:p></o:p></pre><pre><o:p> </o:p></pre><pre> <o:p></o:p></pre>
<blockquote style='margin-top:5.0pt;margin-bottom:5.0pt'><pre>currently creating our disks using the Live CD. I assume this is where I<o:p></o:p></pre><pre>create the second partition?<o:p></o:p></pre><pre> <o:p></o:p></pre></blockquote>
<pre><o:p> </o:p></pre><pre>Sure. You could also do it from within voyage, assuming that there is<o:p></o:p></pre><pre>free space to partition.<o:p></o:p></pre><pre> <o:p></o:p></pre>
<blockquote style='margin-top:5.0pt;margin-bottom:5.0pt'><pre>Also, do you know if this second partition included in a disk replication<o:p></o:p></pre><pre>using DD?<o:p></o:p></pre><pre><o:p> </o:p></pre><pre> <o:p></o:p></pre></blockquote>
<pre>If you dd the whole disk (eg. /dev/sda), then yes all partitions are<o:p></o:p></pre><pre>preserved in the resulting image. If you want to carve out one of these<o:p></o:p></pre><pre>partitions from the resulting single image, things can get complicated<o:p></o:p></pre><pre>(I had to do it once, I documented this here:<o:p></o:p></pre><pre><a
href="http://meganerd.ca/site/node/11">http://meganerd.ca/site/node/11</a>). A better solution in this case is to<o:p></o:p></pre><pre>dd each partition individually (eg. /dev/sda1 and /dev/sda2). An even<o:p></o:p></pre><pre>better solution is to use partimage.<o:p></o:p></pre><pre>-----BEGIN PGP SIGNATURE-----<o:p></o:p></pre><pre>Version: GnuPG v1.4.6 (GNU/Linux)<o:p></o:p></pre><pre>Comment: Using GnuPG with Mozilla - <a
href="http://enigmail.mozdev.org">http://enigmail.mozdev.org</a><o:p></o:p></pre><pre><o:p> </o:p></pre><pre>iD8DBQFKAsFHwRXgH3rKGfMRAg80AKCgUeMKH8siiMHcPD/ZT4LmcxlrmgCfcrsp<o:p></o:p></pre><pre>+TdysYMhRf+wc0MrCXBcZs0=<o:p></o:p></pre><pre>=IKL0<o:p></o:p></pre><pre>-----END PGP SIGNATURE-----<o:p></o:p></pre><pre><o:p> </o:p></pre><pre><o:p> </o:p></pre><pre>_______________________________________________<o:p></o:p></pre><pre>Voyage-linux mailing list<o:p></o:p></pre><pre><a
href="mailto:Voyage-linux@list.voyage.hk">Voyage-linux@list.voyage.hk</a><o:p></o:p></pre><pre><a
href="http://list.voyage.hk/mailman/listinfo/voyage-linux">http://list.voyage.hk/mailman/listinfo/voyage-linux</a><o:p></o:p></pre><pre><o:p> </o:p></pre><pre> <o:p></o:p></pre></div>
</body>
</html>