<html><head></head><body bgcolor="#FFFFFF"><div><br></div><div>On Nov 12, 2011, at 11:30 AM, Jerry <<a href="mailto:mythtv@hambone.e4ward.com">mythtv@hambone.e4ward.com</a>> wrote:<br><br></div><div></div><blockquote type="cite"><div>On Fri, Nov 11, 2011 at 11:37 PM, Mark Lord <span dir="ltr"><<a href="mailto:mythtv@rtr.ca">mythtv@rtr.ca</a>></span> wrote:<br><div class="gmail_quote"><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;">
<div class="im">On 11-11-11 07:55 PM, MythTV wrote:<br>
> On 11/11/2011 05:52 PM, <a href="mailto:networks1@cox.net">networks1@cox.net</a> wrote:<br>
>> ============================= Thanks for the input. So I had a look at<br>
>> the entry in fstab and right now it's "defaults." Did you change to<br>
>> defaults,nobarrier or just replace it with nobarrier? I also found<br>
>> <a href="https://wiki.archlinux.org/index.php/Ext4" target="_blank">https://wiki.archlinux.org/index.php/Ext4</a> which says "Users can<br>
>> improve performance with the nobarrier option when mounting the disk,<br>
>> but this can be dangerous [2] and may result in data loss or<br>
>> corruption after power failures. To turn barriers off, add the option<br>
>> barrier=0 to the desired filesystem" So I presume that's the right<br>
>> thing to do, but again append it after defaults, or replace? Steve<br>
><br>
> Just append it:<br>
><br>
> defaults,nobarrier<br>
<br>
</div>Or even simplier, just put: nobarrier<br>
in place of "defaults".<br><br></blockquote><div>I am experiencing the same issues. I am hesitant to use the nobarrier option. I have a UPS but it doesn't seem like the safest thing.<br><br>Let me also say that I am in a little over my head here. I did some searching on in the mythtv-users archive and came up with this message from last month:<br>
<br><a href="http://www.mailinglistarchive.com/html/mythtv-users@mythtv.org/2011-10/msg00529.html">http://www.mailinglistarchive.com/html/mythtv-users@mythtv.org/2011-10/msg00529.html</a><br><br>I followed the suggestions; that is, appending journal_async_commit,noatime,nodiratime to my mount options in /etc/fstab/ Previously, mythfilldatabase took 20 minutes to run (data was already present). Now, it takes 10 minutes. It's still not as fast as using nobarrier but it's a vast improvement.<br>
<br>I'm still open to suggestion. Your mileage may vary. :)<br></div></div>
</div></blockquote><blockquote type="cite"><div><span>______________________________</span><br></div></blockquote><br><div>I would add to this that even after adding barrier=0 it speeded up MySQL but the frontend and setup interfaces are extremely sluggish. I don't know if this is because of the disk or Gnome 3, which others have warned is a resource hog. If its the latter it must be a pretty big hog because I'm running on a dual core 3ghz processor. </div></body></html>