<html><head><style type="text/css"><!-- DIV {margin:0px;} --></style></head><body><div style="font-family:arial,helvetica,sans-serif;font-size:14pt"><div><br></div><div style="font-family:arial, helvetica, sans-serif;font-size:14pt"><br><div style="font-family:times new roman, new york, times, serif;font-size:12pt"><font size="2" face="Tahoma"><hr size="1"><b><span style="font-weight: bold;">From:</span></b> Raymond Wagner <raymond@wagnerrp.com><br><b><span style="font-weight: bold;">To:</span></b> Discussion about MythTV <mythtv-users@mythtv.org><br><b><span style="font-weight: bold;">Sent:</span></b> Sat, July 9, 2011 3:12:22 PM<br><b><span style="font-weight: bold;">Subject:</span></b> Re: [mythtv-users] Storage Group Disk Scheduler<br></font><br> On 7/9/2011 17:21, Dave Stuart wrote: <blockquote type="cite"> <div style="font-family:arial, helvetica, sans-serif; font-size:14pt;color:rgb(0, 0, 191);">
<div>I have a backend that I am running on a low memory system. I have mounted 7 filesystems on 2 hard drives. The filesystems have to be small enough to let fsck work without running out of memory. The scheduler seems to think that each of the 7 mounts is on a different physical disk, and therefore the disk I/O scheduler option is not working correctly. Is there any way to make this work?<br> </div> </div> </blockquote> <br> Switch to a filesystem that uses journaling to prevent lengthy fscks, and allows for single partitions. Switch to a filesystem whose fsck application is not so memory intensive, and allows for single partitions. Stop uncleanly unmounting partitions, such that lengthy fscks are no longer necessary. Buy more memory for your MythTV system, or failing that, buy a new MythTV system
such that you can buy more memory for it<br> <br> Could you give a bit more detail about this system with insufficient memory to run fsck? I had no trouble running a fsck on a 2TB EXT3 partition earlier this week using my laptop. My laptop still has the same 384MB of memory it shipped with when I bought it over 10 years ago.<br><br><br><span style="font-weight: bold;"><span style="color: rgb(0, 0, 255);"><span style="font-family: arial,helvetica,sans-serif;">Thank you for your reply.<br><br></span></span></span><span style="color: rgb(0, 0, 255);"><span style="font-family: arial,helvetica,sans-serif;"><span style="font-weight: bold;">The device that I am using to run the backend is a goflex net using the plugapps instructions. It has 128mb of ram.</span></span></span> <span style="color: rgb(0, 0, 255);"><span style="font-weight: bold;"><span style="font-family: arial,helvetica,sans-serif;">I have a
1tb drive and a 1.5tb drive that I am using to store shows. I did try at one time to run a fsck on the 1tb drive and it had not finished after 3 hours.<br><br>I am using ext3 filesystem (journaling), but I want to be able to use fsck as a backup.<br><br>I am not uncleanly unmounting partitions. <br><br>More memory is not an option for this machine, and this is the machine that I will be using.<br><br>Can you recommend a filesystem that would be better to use for this application? Should I specify format parameters to make the fsck use less memory?<br><br>In any case, it seems to me that the mythtv scheduler should be using the device rather than the filesystem to determine the 'weight'. I can imagine a number of scenarios when using storage groups where this would be a good idea.<br><br>Thanks<br><br>dave<br><br></span></span></span> </div></div> </div></body></html>