<!DOCTYPE html>
<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
</head>
<body>
<div class="moz-cite-prefix">On 11/17/23 10:59, Ram Ramesh wrote:<br>
</div>
<blockquote type="cite"
cite="mid:85c76086-37a5-4514-993f-fbca758eac7d@gmail.com">
<meta http-equiv="content-type" content="text/html; charset=UTF-8">
I have two storage directories of vastly different sizes (1 TB SSD
and 10+TB spinning RAID1). I had them both in default group and
balancing algorithm as "combined" with default setting. I thought
that myth is smart and will figure out and favor SSD over spinning
disk when possible. That did not work. So, I changed the algorithm
to "Balanced free percent" and was hoping it will keep about the
same % of free space in both disks. I noticed today that SSD has
about 13% (96G) use (87% (660G) free) and spinning disks have
about 94% (12T) use (6% (770G) free). This means next recording
should go to SSD. However, it is now writing to my spinning disks.
What did I do wrong?<br>
<br>
Distribution: Debian bookworm (Linux 6.1.10)<br>
Myth: 31+fixes from debian-multimedia
(31.0+fixes20201214.gite9b795a1e4-dmo0~bpo10+1 as per apt)<br>
<br>
I only changed the storage priorities yesterday and the new
recording is the first one after that. Do I need to wait or reboot
after changing storage balancing algorithm before it takes effect?<br>
<br>
Regards<br>
Ramesh<br>
<br>
</blockquote>
Found the problem. I had not started mythtv-setup with sufficient
privilege to kill the running backend. So, even though it reported
that it stopped backend, it did not. Thus my update did not make it
to backend at all. Once I restarted backend manually, it seem to
work as expected.<br>
<br>
I wish backend-setup caught this error and failed instead of making
me believe that everything is fine. Anyway, I am running an older
version, and may be it is fixed already.<br>
<br>
Regards<br>
Ramesh<br>
<br>
</body>
</html>