<br><br><div class="gmail_quote">On 21 October 2010 09:23, Scott <span dir="ltr"><<a href="mailto:scott@frak.ms">scott@frak.ms</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin: 0pt 0pt 0pt 0.8ex; border-left: 1px solid rgb(204, 204, 204); padding-left: 1ex;">
<br>
On Oct 20, 2010, at 5:22 PM, Brent Bolin wrote:<br>
> My current setup is a back end with raid disk storage and tuners. I<br>
> also have a back end running in a Xen environment as a guest helping<br>
> with commercial flagging.<br>
><br>
> I also just upgraded my network to GB today.<br>
><br>
> Flagging from the mythtv guest helps take the cpu load off the primary<br>
> back end, but still puts a stress on disk I/O.<br>
><br>
> I've been toying with the idea of creating another storage directory<br>
> for mythtv recordings and that being an NFS mount from the primary<br>
> back end. One of my main concerns is creating a complected<br>
> configuration.<br>
><br>
> Is this the only way to spread disk usage between systems(NFS)?<br>
<br>
Are the disks really stressed during commflag? I have a single disk SATA 7200 RPM drive that records 3 HD streams from a HDHR while doing commflag at the same time. Disk IO has never been a bottleneck on the system.<br>
<br>
If you do want to spread the work, your best bet for simplicity is more physical drives in the same system. You can use mdtools or LVM to strip data across two disks. to spread the work.<br>
<font color="#888888"></font><br></blockquote></div><br>or you can just add more disks to the Storage group.<br><br>Cheers,<br><br>Anthony<br><div style="visibility: hidden; left: -5000px;" id="avg_ls_inline_popup"></div>
<style type="text/css">#avg_ls_inline_popup{position: absolute;z-index: 9999;padding: 0px 0px;margin-left: 0px;margin-top: 0px;overflow: hidden;word-wrap: break-word;color: black;font-size: 10px;text-align: left;line-height: 130%;}</style>