Jump to content

miketew

Members
  • Posts

    21
  • Joined

  • Last visited

Posts posted by miketew

  1. 8 hours ago, jortan said:

     

    The ZFS plugin isn't intended to replace the Unraid array (with it's flexibility to mix and match disks), but rather to replace the functionality otherwise provided by the cache drive/pool (ie. BTRFS)

     

    When ZFS is officially supported in Unraid (which has been hinted at), that will still be the case.

     

    edit:  That said, ZFS raidz expansion is now a thing, and there has always been the option to fairly easily expand arrays with mirrored pairs (which is generally regarded as the best pool topology)


    yeah, I have no interest in expansion requiring 2 disks for the size of 1 each time 😛 but I was not aware ZFS was that far along with expansion officially, that's awesome.

  2. On 11/20/2022 at 11:55 AM, gyto6 said:

    You must destroy and create a pool with each disk. Copy your data to an external USB drive temporarily to create your new zpool.

     

    in this case, unraid's ZFS plugin essentially renders part of unraid's draw (mix and match disks) somewhat moot, as it behaves just like a normal ZFS zpool with the inability to scale out or scale up. is that right?

  3. A couple thoughts... maybe I'm missing something. Isn't SnapRAID essentially the same concept as Unraid - parity calculated "externally" - Unraid does it at runtime, SnapRAID does it on request, but neither provides bitrot protection via detection. Simply by restoration (if I detect a file has become corrupted, I can restore from parity)

     

    Also would be very curious how ZFS gets introduced, instead of XFS or BTRFS for a disk's filesystem, it would be simply a single disk zvol? I would expect performance could be more affected then. Also, seems like the only benefit there would be help detecting bitrot happening (which is a good thing)

  4. I would use it for replacing a couple ZFS-based systems - right now I have two 16x1.5tb systems (in 2 groups of raidz2 each) that are aging a little bit. Also hate dealing with solaris. I get 16tb usable or so in each.

     

    Getting a 15 bay unit with 3TB disks = 42tb roughly usable storage right? That would be able to handle replacing both of these monster machines, in a single 15 bay unit.

     

    (I want to know more about this 20 bay unit mentioned earlier in the year!)

     

    Biggest thing for me is cooling and acoustics. Nobody addresses it that well still to this day.

     

    I use it to store my DVD archive, digital hoarding, etc.

  5. since this is a storage OS first, all priority should be on storage related things. performance should be key.

     

    important:

    - increase write performance

    - automatic save/restore of Flash 'config' directory to a designated hard disk file

    - email alerts

    - hot spares

     

    less of a concern... to me this is just more bells and whistles that should be very low priority (this is where SOHO units get lost from the primary goal of a reliable and performant storage unit in my opinion...)

    - UPnP

    - Integrated wizd server

    - Slimserver 6.5.0. support

    - other misc servers, eg, "Galleon"

    - hamachi vpn

     

  6. The List:

    - support multi-core processors & memory beyond 1GB

    - add cpuspeed support

    - support additional file systems such as XFS, NTFS

     

    - NFS support

    - AFP support

     

    - get time from the internet (ntpd)

     

    if this is a linux kernel-based solution, isn't this as easy as compiling these in to the kernel (or modules?) - i guess then just adding them into the UI is all that is left...

     

    and ntp is real easy :) i actually don't use ntpd, i use ntpdate, and then i schedule it to run via cron every hour. would be easy to allow the user to define their own servers and how often they want it to update.

     

×
×
  • Create New...