<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<html>
<head>
<meta content="text/html; charset=ISO-8859-1"
http-equiv="Content-Type">
</head>
<body bgcolor="#ffffff" text="#000000">
On 7/9/2011 17:21, Dave Stuart wrote:
<blockquote
cite="mid:1310246477.18322.YahooMailRC@web111723.mail.gq1.yahoo.com"
type="cite">
<style type="text/css"><!-- DIV {margin:0px;} --></style>
<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>
</body>
</html>