• Login
  • Register
  • Login Register
    Login
    Username/Email:
    Password:
    Or login with a social network below
  • Forum
  • Website
  • GitHub
  • Status
  • Translation
  • Features
  • Team
  • Rules
  • Help
  • Feeds
User Links
  • Login
  • Register
  • Login Register
    Login
    Username/Email:
    Password:
    Or login with a social network below

    Useful Links Forum Website GitHub Status Translation Features Team Rules Help Feeds
    Jellyfin Forum Support General Questions metadata storage

     
    • 0 Vote(s) - 0 Average

    metadata storage

    metropical
    Offline

    Member

    Posts: 102
    Threads: 27
    Joined: 2024 Apr
    Reputation: 0
    Country:United States
    #1
    2026-05-29, 04:25 PM
    I just moved my music to a 4T WD Blue in a MacPro3,1.
    The server runs on a LAN'd 2018 Mac mini.
    Would moving the metadata to the internal SSD of the mini be a space and efficiency upgrade?
    If that is possible, how would that be done?
    Or perhaps point me to something to read that I haven't yet found.
    2018 3.2 GHz 6-Core Intel Core i7 mini w/64G
    MacOS 15.7.7 Sequoia
    JFS 10.10.7 - JFMP 1.12
    Music is on 4TB WD 5400prm blue in cMP3,1 via unmanaged TP switch.




    TheDreadPirate
    Offline

    Community Moderator

    Posts: 15,502
    Threads: 11
    Joined: 2023 Jun
    Reputation: 468
    Country:United States
    #2
    2026-05-29, 04:34 PM
    Is your music metadata currently in NFO files? IIRC, Jellyfin reads those when they are initially added to the library. After the initial scan, metadata is retrieved and served from the database until a change in the NFO is detected. I THINK if you simply removed the NFOs the metadata still exists in the Jellyfin database. It would be worth testing this out for a single album/artist.
    Jellyfin 10.11.11 (Docker)
    Debian 13 w/Xanmod amd64v3 LTS kernel
    AMD Ryzen 5500 w/32GB DDR4
    Intel Arc A380
    OS drive - SK Hynix P41 1TB
    ZFS Storage pool
        vdev1 - 6x WD Red Pro 6TB CMR in RAIDZ1
        vdev2 - 3x WD Red Pro 18TB CMR in RAIDZ1
    [Image: GitHub%20Sponsors-grey?logo=github]
    metropical
    Offline

    Member

    Posts: 102
    Threads: 27
    Joined: 2024 Apr
    Reputation: 0
    Country:United States
    #3
    2026-05-30, 01:38 PM (This post was last modified: 2026-05-30, 01:38 PM by metropical.)
    nfo, so it would seem.
    are you saying that if the nfo move worked and all was intact, then moving the metadata db to the internal should be OK?
    Just to clarify, the internal on the mini.
    All the music still resides on a 4TB in a LANd MacPro.
    2018 3.2 GHz 6-Core Intel Core i7 mini w/64G
    MacOS 15.7.7 Sequoia
    JFS 10.10.7 - JFMP 1.12
    Music is on 4TB WD 5400prm blue in cMP3,1 via unmanaged TP switch.




    metropical
    Offline

    Member

    Posts: 102
    Threads: 27
    Joined: 2024 Apr
    Reputation: 0
    Country:United States
    #4
    2026-05-30, 06:42 PM
    oh silly me. just looked and the meta is on the internal of the mini. giggle, giggle, giggle.
    2018 3.2 GHz 6-Core Intel Core i7 mini w/64G
    MacOS 15.7.7 Sequoia
    JFS 10.10.7 - JFMP 1.12
    Music is on 4TB WD 5400prm blue in cMP3,1 via unmanaged TP switch.




    TheDreadPirate
    Offline

    Community Moderator

    Posts: 15,502
    Threads: 11
    Joined: 2023 Jun
    Reputation: 468
    Country:United States
    #5
    2026-05-30, 07:24 PM
    (2026-05-30, 01:38 PM)metropical Wrote: nfo, so it would seem.
    are you saying that if the nfo move worked and all was intact, then moving the metadata db to the internal should be OK?
    Just to clarify, the internal on the mini.
    All the music still resides on a 4TB in a LANd MacPro.

    Yes.  When you add your music with the NFO, the NFO is read during the library scan and that information is put into the Jellyfin database.  When you view that music in your client, it is not retrieving the information from the NFO it is reading it from the database.

    If you want to keep your NFOs to ensure consistent metadata if you ever had to rebuild Jellyfin, you can keep them.  If you want to reclaim the space,  you SHOULD be able to delete the NFOs since the data has already been ingested into Jellyfin's DB.  I can't imagine the disk space recovered would amount to much.

    However, test this assumption on a single album or artist before mass deleting all your NFOs.
    Jellyfin 10.11.11 (Docker)
    Debian 13 w/Xanmod amd64v3 LTS kernel
    AMD Ryzen 5500 w/32GB DDR4
    Intel Arc A380
    OS drive - SK Hynix P41 1TB
    ZFS Storage pool
        vdev1 - 6x WD Red Pro 6TB CMR in RAIDZ1
        vdev2 - 3x WD Red Pro 18TB CMR in RAIDZ1
    [Image: GitHub%20Sponsors-grey?logo=github]
    metropical
    Offline

    Member

    Posts: 102
    Threads: 27
    Joined: 2024 Apr
    Reputation: 0
    Country:United States
    #6
    2026-05-31, 06:57 PM
    (2026-05-30, 07:24 PM)TheDreadPirate Wrote:   I can't imagine the disk space recovered would amount to much.

    However, test this assumption on a single album or artist before mass deleting all your NFOs.

    yes, deleting nfo looks like it would amount to pocket change disk space recovery. Average nfo is 2kb.
    thanks for looking in.
    2018 3.2 GHz 6-Core Intel Core i7 mini w/64G
    MacOS 15.7.7 Sequoia
    JFS 10.10.7 - JFMP 1.12
    Music is on 4TB WD 5400prm blue in cMP3,1 via unmanaged TP switch.




    « Next Oldest | Next Newest »

    Users browsing this thread: 1 Guest(s)


    • View a Printable Version
    • Subscribe to this thread
    Forum Jump:

    Home · Team · Help · Contact
    © Designed by D&D - Powered by MyBB
    L


    Jellyfin

    The Free Software Media System

    Linear Mode
    Threaded Mode