Hello Everyone

I have a Knoppmyth box running without any noticable problems, except that I can't rip a DVD because the temp files in /var/lib/mythdvd/temp fill out the root partition and that ndiswrapper is unusable. I have another posting on the ndiswrapper issue that I am hoping that someone will get back to me with a solution..

When I start ripping a DVD, the temp files get written to /var/lib/mythdvd/temp and this quickly fills out the root partition. As a result, any DVD ripping fails. By the way, I performed the stock auto install and the disk partitions were created automatically. Currently, hda1 (root) is 5GB of which 2.6GB are available.

I searched for this issue in this forum and found three postings about the same issue without a finite solution. If the installation process was not allowed to continue on its own, what is the way to make it do it?


Cheers,

Delyan

well I'm sure that temp dir is a setting somewhere, though I admit I don't know where, but an inelegant solution would be to create a temp dir under /myth and symlink /var/lib/mythdvd/temp to it.

_________________
Have a question search the forum and have a look at the KnoppMythWiki.

Xsecrets

Interesting... I guess I'll have to remember to double check this as the default should be /myth/tmp.

_________________
cesman

When the source is open, the possibilities are endless!

Cesman:

If you need, I can provide you with access to the server. I can also duplicate the issue while you are monitoring. Please let me know.

No need thanks. I just need to verify that KnoppMyth.sql is accurate from my end.

Cesman:

I see that in KnoppMyth.sql, for DB table "settings" the data field for value "DVDRipLocation" is "/myth/tmp" so it is correct:

INSERT INTO `settings` (`value`, `data`, `hostname`) VALUES ('DVDRipLocation','/myth/tmp', 'MythTVhost');


However, in the database it is "/cache/mythdvd/temp/", which is incorrect. The same information goes into the backup file mythconverg.sql after performing a backup.

mysql> select * from settings where value = 'DVDRipLocation';
+----------------+----------------------+----------+
| value | data | hostname |
+----------------+----------------------+----------+
| DVDRipLocation | /cache/mythdvd/temp/ | mythtv |
+----------------+----------------------+----------+
1 row in set (0.00 sec)

mysql>



I was wondering if a simple update statement in mysql will fix the issue. Is there anything else that I should be aware of before performing this test?


Also, I wanted to ask if there is a way to check the consistency of the DB tables against the correct KnoppMyth.sql. I suppose that there is a default database with data that is not relevant to the latest KnoppMyth release, which is supposed to be updated with the KnoppMyth.sql during install? Do you have any suggestions?


Thanks again for your assistance!

nonanone

Another important detail is that the temporary files are actually written in /var/lib/mythdvd/temp and this directory path is neither in the KnoppMyth.sql nor in the DB.

Is this path hardcoded in the mtd binary?

Do you know the way to correct this?

Well, if it really is hardcoded, you could create the directory, at least as a symlink to where you really want the stuff to go. Or maybe binary edit the executable and put in a "correct" path of the same or a shorter length. (BTW - I DO NOT recommend that second alternative, that's very advanced evil.)

tjc:

My point here was not really to find a way to circumvent the symptom, but to get to the bottom of the issue. My competence in Linux and DB is sufficient to at least get me by and I already have a way to go around this. However, can I be sure that the next upgrade will not mess things up even more because of my customization??? No one is really insured against this, so I would prefer to stay on the safe side.

I see several problems here for which I would like to make my contribution. First and most important is the no apparent reason for "the installation process was not allowed to continue on its own". On the other hand, the mtd daemon uses one directory for temp files, the upgrade sql file has a different one, and the lead developer for this project suggests another value.

Thank you for the suggested "advanced" alternatives. I will definetely consider them

Below is the fix that worked for me. The following sql statement should be executed in the "mythconverg" database:

update settings set data = "/myth/tmp/" where value = "VideoStartupDir";

In terms of what is set via KnoppMyth.sql, /myth/tmp is accurate. If for whatever reason, the MythTV db settings got reset (and that would be to the MythTV defaults) this explains the what happened to your setup.

_________________
cesman

When the source is open, the possibilities are endless!

There might be other possible inconsistencies in the database due to whatever reason... What is the recommended way to check the difference between my current database and the intended KnoppMyth database?