Reply to thread

Message

<blockquote data-quote="obelisk3847" data-source="post: 871628" data-attributes="member: 113698">I have a very large collection of about 1300 movies on 12 sources and was/have migrated them onto a Linux Greyhole server so I am now down to 2 sources. The procedure of marking drives for removal is quite straight forward but I ended up having about 200 to 250 movies that were not detected. When I looked in the database they were all VIDEO_TS.IFO file entries that did not have hash values. It seems like the MKV files which represent the bulk of my collection were fine though.&nbsp;I actually ended up with double entries because the original entries were effectively orphaned and the movies on the new path were detected as new. My ultimate solution was to role back the database (I had a backup) and turn off the gateway on the PC so it could talk to the Greyhole server but not any of the Internet Scrapers which gave me time to clean up the database with SQL without getting duplicate entries.&nbsp;Strangely enough it wasn't 100% of my DVD based movies using VIDEO_TS.IFO orphaned as some of them were detected on the new path even though they didn't have a hash entry. I was curious what is the mechanism you use to compare the database entry to the file system entry if hash is not available. Also, has anyone else had any of these issues or is it more likely something specific to my database. I tried it 2 or 3 times and noticed that it was always the same movies that were orphaned so not sure if that provides anything of use. I think I still have copies somewhere of the database at baseline and the database with the orphaned entries should you like to see it.</blockquote>

[QUOTE="obelisk3847, post: 871628, member: 113698"] I have a very large collection of about 1300 movies on 12 sources and was/have migrated them onto a Linux Greyhole server so I am now down to 2 sources. The procedure of marking drives for removal is quite straight forward but I ended up having about 200 to 250 movies that were not detected. When I looked in the database they were all VIDEO_TS.IFO file entries that did not have hash values. It seems like the MKV files which represent the bulk of my collection were fine though. I actually ended up with double entries because the original entries were effectively orphaned and the movies on the new path were detected as new. My ultimate solution was to role back the database (I had a backup) and turn off the gateway on the PC so it could talk to the Greyhole server but not any of the Internet Scrapers which gave me time to clean up the database with SQL without getting duplicate entries. Strangely enough it wasn't 100% of my DVD based movies using VIDEO_TS.IFO orphaned as some of them were detected on the new path even though they didn't have a hash entry. I was curious what is the mechanism you use to compare the database entry to the file system entry if hash is not available. Also, has anyone else had any of these issues or is it more likely something specific to my database. I tried it 2 or 3 times and noticed that it was always the same movies that were orphaned so not sure if that provides anything of use. I think I still have copies somewhere of the database at baseline and the database with the orphaned entries should you like to see it. [/QUOTE]

Verification