2024-04-04, 07:30 AM
(This post was last modified: 2024-04-10, 12:04 PM by killminusnine. Edited 2 times in total.)
Hi,
I just had a quite similar bad experience with Jellyfin (never occured with DS Video, Plex and Emby) : in my films library, 13TB were deleted (about 5500 films). In fact, after analysis of this "issue", Jellyfin didn't erase anything ... but ... during indexation and metadata gathering, Jellyfin linked wrong metadata with a whole folder named "HD" (containing these 5500 films) as if it was a single file (not a directory), linked with a film named "HDCS" or a thing like that. Because this "ghost" film matched with nothing, I made the HUGE error to delete it (with an alert message from Jellyfin that it can't be reversed, that I have ignored) ... and it took a very long time. At this point I understood something gone wrong, but too late to abort. Fortunately, my server is a NAS Synology DS220+ in RAID1 mode, and with a btrfs filesystem with daily snapshots. I have recovered the whole deleted folder, and I'm not upset against Jellyfin, which is a very good software, but this bad experience may warn everybody that Jellyfin may make very insignificant errors that can be amplified as a disaster by hazardous actions like those I have done, misunderstanding at this moment what really was going on.
I just had a quite similar bad experience with Jellyfin (never occured with DS Video, Plex and Emby) : in my films library, 13TB were deleted (about 5500 films). In fact, after analysis of this "issue", Jellyfin didn't erase anything ... but ... during indexation and metadata gathering, Jellyfin linked wrong metadata with a whole folder named "HD" (containing these 5500 films) as if it was a single file (not a directory), linked with a film named "HDCS" or a thing like that. Because this "ghost" film matched with nothing, I made the HUGE error to delete it (with an alert message from Jellyfin that it can't be reversed, that I have ignored) ... and it took a very long time. At this point I understood something gone wrong, but too late to abort. Fortunately, my server is a NAS Synology DS220+ in RAID1 mode, and with a btrfs filesystem with daily snapshots. I have recovered the whole deleted folder, and I'm not upset against Jellyfin, which is a very good software, but this bad experience may warn everybody that Jellyfin may make very insignificant errors that can be amplified as a disaster by hazardous actions like those I have done, misunderstanding at this moment what really was going on.