Zimeic

Members
 View Profile  See their activity

  • Posts

    5

  • Joined

  • Last visited

Zimeic's Achievements

Noob

Noob (1/14)

0

Reputation

  1. Zimeic
    Allright, i think i figured out how to implement my wonky setup 😉 Just out of curiousity, i saw a trim section in the scheduler options, is that something different?
  2. Zimeic
    I was asking if i'm forced to to run a multi drive pool in a raid of some sort like ZFS instead of XFS. I think I found an answer to my question after more research though: Up until now i was under the impression i have to group drives in some sort of group/pool/array/whatever before pointing a share to that group to utilize all drives included in that group. But as it turns out i can specify individual drives to use per share, so i'll just chuck all HDDs/SSDs into the array and create the 'groups' that way.
  3. Zimeic
    Can as in optional? So i could have two pools (with the aforementioned 3x HDD and 3x SSD) each utilizing the classic individual unraid strategy? That would probably work for what I need. I could just set up a docker or cron job that syncs from the SSD pool to the HDD pool and for the 'classic' pool uses i'd have a third cache pool.
  4. Zimeic
    Ok, next option i guess would be to have the cached shares on a seperate SSD only array and manually sync changes made there to an HDD array share/folder. Just to be clear on the terminology, if i have 3x HDDs and 3x SSDs that should be in a 'group' each, would that two arrays with three devices each or an array with two pools containing three devices each?
  5. Zimeic
    Hi there! From what i understand, the unraid mover can move data from the primary storage (SSD cache) to the secondary storage (HDD array) and in reverse. Is it possible to keep predefined files/folders/shares on the cache as well as the array? My goal is to have the data on the SSD cache for reads and writes so that i don't have to spin up any disks when they happen. At some scheduled point all changes made to the data on the cache will be synced to the array in one whole swoop. Ideally, this functionality should exists parallel to regular mover/cache functionality (write cache for array that gets moved off the cache regularly, living space for vms and its data).