Recent content by _Gea

https://omnios.org/releasenotes.html Unlike Oracle Solaris with native ZFS, OmniOS stable is compatible with Open-ZFS but with its own dedicated software repositories per stable/lts release. This means that a simple 'pkg update' gives the newest state of the installed OmniOS release and not a...

New release of ZFS on Windows zfs-2.2.3rc4, it is fairly close to upstream OpenZFS-2.2.3 with draid and Raid-Z expansion https://github.com/openzfsonwindows/openzfs/releases/tag/zfswin-2.2.3rc4 rc4: Unload BSOD, cpuid clobbers rbx Most of the time this is not noticeable, but in...

Raspberry 4 can be managed remotely by the napp-it cs web-gui Just upload folder cs_server and start via perl /path_to_cs_server/start_server_as_admin.pl # uname -a raspberry4~192.168.2.89 Linux phoscon 5.10.103-v7l+ #1529 SMP Tue Mar 8 12:24:00 GMT 2022 armv7l GNU/Linux ps aux pi 30136...

Release Notes for OmniOS v11 r151048 r151048w (2024-04-11) Weekly release for w/c 8th of April 2024. https://omnios.org/releasenotes.html Security Fixes For Intel CPUs that are vulnerable to Native Branch History Injection,the kernel now takes steps to scrub the CPU's Branch History Buffer...

How much RAM do I need for napp-it cs RAM for a ZFS filer has no relation to pool or storage size (beside dedup)! Calculate 2 GB for a 64bit OS, add 1-2 GB for a Solaris based filer and 3-4 GB for a BSD/Linux/OSX/Windows based filer for minimal read/write caching or ZFS can be really slow. RAM...

The flavours of ZFS native ZFS in Solaris 11. This is the Unix where ZFS was developped for. The most resource efficient and stable ZFS and propably the fastest one. In 20 years I have not seen as many bug reports up to dataloss than on Linux in a few weeks. Native ZFS is not free nor...

napp-it cs beta, current state (apr.05) Server groups with remote web-management: (BSD, Illumos, Linux, OSX, Windows): ok ZFS (pool,filesystem,snap management): ok on all platforms Jobs (snap, scrub, replication from any source to any destination): ok beside Windows as source or destination...

Another day, another step: Replication between servers is basically working with problems on some combinations. https://forums.servethehome.com/index.php?threads/napp-it-cs-web-gui-for-m-any-zfs-server-or-servergroups.42971/page-3#post-420458

You can`t just give away a file on an USB stick to anyone like you can with *Fat* but that is not the point and for such I use a cloud link now. All of my systems have ZFS so I can just plug an external USB disk (can be 20TB) ex to my Mac, Linux/ Unix or Windows systems and import the pool to...

TrueNAS as a servergroup member - Enable SSH, allow root (sharing options) or SMB - Copy napp-it cs_server to a filesystem dataset ex tank/data (/mnt/tank/data) - open a root shell and enter: perl /mnt/tank/data/cs_server/start_server_as_admin.pl Add Truenas to your servergroup (ZFS...

If you want to move your AiO setup from ESXi to Proxmox, read https://forums.servethehome.com/index.php?threads/napp-it-for-proxmox.32368/#post-419886

If you want to move your OmniOS AiO setup from ESXi to Proxmox, read https://forums.servethehome.com/index.php?threads/napp-it-for-proxmox.32368/#post-419886

There are use cases where you still need a *Fat* variant and a data loss or undetected bad file is not relevant. There are use cases where data security is the main concern like a secure data move via stick or backup via checksum protected zfs send to a removeable ZFS pool with copies=2 on USB...

ok, but then say - no to checksums (no report on bad files) - no to Copy on Write (undamaged filesystems after a crash/remove during write) - no to transparent compress - no to transparent encryption - no to autorepair files on bad blocks with ZFS and copies=2

A napp-it replication uses dedicated snaps (*_repli.._nr_n) and protects them from autosnap so normally you should have a common base snap. If not you cannot sync them again. Rsync can sync files but not make filesystems exact identical. Usually, you rename the target filesystem in such a case...