2024-07-21, 10:37 PM
(This post was last modified: 2024-07-21, 10:39 PM by Huecuva. Edited 1 time in total.)
The NAS is not actually network attached to the jellyfin server. ~/Storage is a mounted 18TB RAIDZ attached to the server itself that is hosting jellyfin. It is only NAS to the rest of the LAN. Is that still not good? I suppose I could make a directory in ~/ which is 45GB and symlink to that instead. Would that be better?
Regarding the link Efficient_Good posted above: after messing around with du a bit, it seems like when I du -L /var it now says it's 6GB and du -L ~/Storage/var is 3GB and du /var is 3GB. so it looks like I might have duplicate metadata after simply creating the symlink, since I copied everything from /var/lib/jellyfin/ to ~/Storage/var before creating the symlink. Do I not need to copy? Should I copy first, then delete from /var before creating the symlink? I'm not sure how to fix this. Though, I think if I create a directory in ~/ I can start over.
Regarding the link Efficient_Good posted above: after messing around with du a bit, it seems like when I du -L /var it now says it's 6GB and du -L ~/Storage/var is 3GB and du /var is 3GB. so it looks like I might have duplicate metadata after simply creating the symlink, since I copied everything from /var/lib/jellyfin/ to ~/Storage/var before creating the symlink. Do I not need to copy? Should I copy first, then delete from /var before creating the symlink? I'm not sure how to fix this. Though, I think if I create a directory in ~/ I can start over.
Jellyfin 10.9.8
Debian 11 Bullseye (Proxmox qemu VM)
4 cores, 1 socket
8GB RAM
OS Drive: 64GB
GPU passthrough: GTX1070
Storage SATA passthrough: 2x18TB HDD RAIDZ
Debian 11 Bullseye (Proxmox qemu VM)
4 cores, 1 socket
8GB RAM
OS Drive: 64GB
GPU passthrough: GTX1070
Storage SATA passthrough: 2x18TB HDD RAIDZ