<br><br><div class="gmail_quote">On Feb 7, 2008 4:28 PM, R. G. Newbury <<a href="mailto:newbury@mandamus.org">newbury@mandamus.org</a>> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;">
<div><div></div><div class="Wj3C7c"><br></div></div>The better solution, IMHO, is small disk for the OS with at least 2<br>partitions, and rsyncing the important data to the the big video disk<br>every night with cron. The OS disk partitions include one for '/', one<br>
for /home (which stores copies of important stuff from /etc too) and<br>possibly one for /var (so that /var/lib/mysql is not on the OS<br>partition). Revising /etc/my.cnf can put mysql at /home/msyql, hitting 2<br>birds with one stone. (This is for Fedora)<br>
<br>Note that if your log files (in /var) fill the partition, then Fedora<br>(linux generally?) may crash and will not re-boot. If running myth you<br>may suddenly find that there are no programs displayed in 'Watch<br>
Recordings' (since mysql cannot now write to<br>/var/lib/mysql/mythconverg). All is not lost however!<br><br>Note that the OS and /home etc will easily fit in 12 or 13 G harddrive,<br>IF you can find one!<br></blockquote>
<div><br class="webkit-block-placeholder"></div><div>Why rsync over a raid1?</div><div><br class="webkit-block-placeholder"></div><div>And, how can I raid 1 two distinct partitions on two distinct disks . . . smells like lvm.</div>
<div><br class="webkit-block-placeholder"></div><div>As far as disk filling goes, I fix that with my frontends by loop-back mounting their root filesystems. So, They have 10Gb or so "disks" that I loopback mount, and *then* nfs export, so that if they go crazy log-wise, they only kill themselves.</div>
<div><br class="webkit-block-placeholder"></div><div>This will be harder with the backend being the server -- I may put /var into it's own partition . . . </div><div><br class="webkit-block-placeholder"></div><div>-Dave</div>
</div>