[SOLVED!] Two backends - one drive being used up

[hedgehog52]

Hope this is the right forum. I have two backends. Both are also frontends. One is my workstation with 12TB of storage across 3 hard drives. The other is the PC next to the TV in the living room with 3TB storage on one drive. I must have misconfigured the way the drives are setup, because I got an out of space warning from the box in the living room today. So, that makes me think that that backend is using its drive as local storage and isn't putting videos across the other 3 drives.

So, what have I misconfigured? Is it something on my workstation, or on the other machine? Both backends should be putting videos across all 4 drives.

Both machines run Debian Jessie Linux.

Added:
I forgot to mention that both machines have all the MythTV drives crosslinked via NFS, and it doesn't seem to be a permissions problem.

[MikeB2013]

I am assuming that when you say videos you are referring to recorded tv.

When you say 2 backends, I presume one is master, the other slave

Check the storagegroup settings on the master mythbackend:
login to mythconverg database (mysql -umythtv -p mythconverg)
select * from storagegroup order by groupname;

Here is what I get, the groupname Default is where recordings go (unless it has been changed), which in my case is 2 drives on mounts /myth/ and /myth3/.

Code: Select all

mysql> select * from storagegroup order by groupname;
+----+-------------+---------------+---------------------------+
| id | groupname   | hostname      | dirname                   |
+----+-------------+---------------+---------------------------+
| 90 | Banners     | myth-server-1 | /myth/mythtv/banners/     |
| 87 | Coverart    | myth-server-1 | /myth/mythtv/coverart/    |
| 85 | DB Backups  | myth-server-1 | /myth/mythtv/db_backups/  |
| 38 | Default     | myth-server-1 | /myth/mythtv/recordings/  |
| 94 | Default     | myth-server-1 | /myth3/mythtv/recordings/ |
| 88 | Fanart      | myth-server-1 | /myth/mythtv/fanart/      |
| 84 | LiveTV      | myth-server-1 | /myth/mythtv/livetv/      |
| 96 | Music       | myth-server-1 | /myth3/mythtv/music/      |
| 92 | MusicArt    | myth-server-1 | /myth/mythtv/musicart/    |
| 89 | Screenshots | myth-server-1 | /myth/mythtv/screenshots/ |
| 93 | Streaming   | myth-server-1 | /myth/mythtv/streaming/   |
| 86 | Trailers    | myth-server-1 | /myth/mythtv/trailers/    |
| 69 | Videos      | myth-server-1 | /myth/mythtv/videos/      |
| 95 | Videos      | myth-server-1 | /myth3/mythtv/videos/     |
+----+-------------+---------------+---------------------------+
14 rows in set (0.00 sec)

mythtv-setup has settings on how to use disk storage (default is Balanced Free Space) which should do what you want.

Mike

[hedgehog52]

Hi Mike,

Thanks for the reply. Here is the response from the master backend for the Default group. For some reason, the "Wendy" backend is only setup for "/Video4/MythTV/Default/". I also see that there are entries for "Musem", "musem", and "musem.local". Should I just use Mysql Workbench to hack this into sanity, or try to manage through the mythtv-setup program?

Bob

Code: Select all

|  75 | Default     | musem       | /Video/MythTV/Default/      |
|  76 | Default     | musem       | /Video2/MythTV/Default/     |
| 127 | Default     | Musem       | /Video3/MythTV/Default/     |
| 142 | Default     | musem.local | /Video/MythTV/Default/      |
| 143 | Default     | musem.local | /Video2/MythTV/Default/     |
| 144 | Default     | musem.local | /Video3/MythTV/Default/     |
| 219 | Default     | wendy       | /Video4/MythTV/Default/     |
| 203 | Default     | musem       | /Video4/MythTV/Default/     |
| 214 | Default     | musem.local | /Video4/MythTV/Default/     |

[MikeB2013]

Bob,

i would use mythtv-setup, one of the things it checks for when you exit is that the Storage Groups are accessible and writable.

As a general rule direct changing of the mythconverg database through mysql is not recommended.

Mike

[hedgehog52]

Thanks Mike. I think it's fixed. I don't know why I didn't have all 4 drives configured on the slave backend. Most likely it's because something else borked and it took so long to fix that that I forgot about the drive setup. Anyway, thanks!

[hedgehog52]

I don't see a way to mark this solved.

[bill6502]

Go to the original post, see if there's an EDIT button and
change the Subject: field.

[hedgehog52]

Oh duh! =) On the linuxquestions forum, there's a special button for solved. And by the way, I did manage to actually prove it's setup correctly now.

Thanks a bunch!