Plex Failing to Ignore NFO/XML/JPG Files - SOLVED

Server Version#:1.18.7.2438

Having an odd issue. When I initiate a library scan for any of my libraries Plex is adding additional files as video’s, like .jpg/.nfo/.xml etc. The end result is hundreds of duplicated episodes with the original file being one copy and the .jpg/.nfo/.xml being the second. My impression was files <300MB would be ignored per:

Not sure exactly when this originated as my server typically initiates partial scans when prompted by Sonarr/Radarr rather than me running full library scans. It also updates itself so this may have been present across multiple versions and I am just noticing it today.

Plex Version: 1.18.7.2438 - Most recent Public

OS: Ubuntu 18.04

Within a Proxmox LXC container, files are on GlusterFS array on debian.

SAMPLE files will be excluded regardless of size.
Otherwise, a 10 MB file, with a valid extension, will be considered.

In order to help further, I will need to see an example which is failing you.

If you can show one isolated case, inclusive of those things which contribute to the problem, I will try to help sort it out.

I will ask now if you have different types of media intermixed, e.g Episodes, movies, songs, pictures, and/or music in the same library type.

NFO files will not be ignored . They are read and the tt number contained therein is used to force the match.

JPG are media files and, if the name matches keywords, it will be used as a cover or season poster.

Thank you for your rapid response.

This issue seems to have originated within the last 48 hours. All media types are in separate folders, for example the “films” folder contains only movies, organized in this manor

/Rootdirectory/Film (Year)/Title (Year).mkv
/Rootdirectory/Film (Year)/fanart.jpg
/Rootdirectory/Film (Year)/movie.xml
/Rootdirectory/Film (Year)/Title (Year).nfo
/Rootdirectory/Film (Year)/poster.jpg

For the above example, when scanned Plex some films are creating multiple matches, 1 with the correct movie, others with a duplicate called “Extrafanart” or something else linking to the “.nfo" or ".xml” or “*.jpg” file. This is occuring in both my films and my television libraries and never occured before 48 hours ago, no changes to the data were made.

Second response here, still testing. For the last 48 hours I have been replacing a drive in my GlusterFS array, basically a distributed file system across multiple servers in which each disk is mirrored to a drive on a separate server. It finally completed and when re-scanning now Plex is behaving as expected.

I can only conclude that this was the issue. I have no idea why this might have had this effect but I appreciate your assistance!

This is important so please help me understand?

  1. you have /
  2. Then you have “ROOTDIRECTORY”

How do you differentiate movies from episodes?

when did movies get episodes ?

@frkhrd_gmail_com

That’s my point.

It’s either a movie or it’s an episode and belong in different library sections.

I should been more clear, I think the user is parsing a moving folder by the structure of the folders he is showing. Season would not be related to his problem. I wonder if he could have turned off the check for samples and that is why plex is adding the small stuff as videos?

@ChuckPa
@frkhrd_gmail_com

As I said above this issue was resolved and looks to be related to my back end storage. For clarification here is how my media is organized, all by the suggested Plex naming conventions, no “mixing” of media types.

Media/Television/Show/Season
Media/Films/Title

All media is stored on a 3 node GlusterFS array in Distributed Replicated volume. I was in the processes of replacing one drive pair, a drive was replaced and the array was rebuilding the replaced drive. During that time any scans from Plex resulted in the above behavior. When the rebuild completed the problem disappeared.

Thanks for clarifying.

Would you please click the appropriate post as ‘Solution’ (under the ellipsis) so the thread marks itself as resolved?

This topic was automatically closed 90 days after the last reply. New replies are no longer allowed.