OpenZFS NAS (BSD, Illumos, Linux, OSX, Solaris, Windows + Storage Spaces) with napp-it web-gui

MS 365 and Nextcloud are the "top dogs" for collaborative work, but at the same time, both are absolute heavyweights in terms of scope, complexity, and features. As a privacy-friendly, in-house option, Nextcloud is conceivable, but far too complex to maintain and secure on the internet, even as a Docker setup.

If you scale back—for example, no mail server, a text editor and spreadsheet that are a bit simpler with a focus on multi-user editing, no AD/LDAP but user.csv import/export instead, plus resource planning (projectors, rooms, personnel), and a lightweight ticketing system, thus targeting schools, a department, a club, or a smaller business—then absolute KISS solutions suddenly become feasible. Thanks to AI integration, even complex tasks can be implemented easily.

This is my approach with cs-team. It runs on any OS even without napp-it, copy and run (approx. 10MB), no database, a single folder on the disk is enough, and with ZFS you get snapshots on top. In the current 0.53 release, I have improved usability once again.

As an open-source git project, it is easily extensible and auditable.

 
new version cs-team 0.61
https://github.com/guenther-alka/cs-team

new manual
https://www.napp-it.org/pdf/cs-team_en.pdf

goal:
80% core functionality of MS Teams/Office 365 with
10% complexity (single file binary, copy and run)

Inhouse Setup
full control over data, incl. Inhouse AI

for multinational teams
(13 languages extendable, incl.main EU languages, Chinese, Japanese, Russian)

or higher education institutions and schools, as well as students with a migration background
(13 languages incl. Arabic, Ukrainian, Turkish, easily expandable)
 
Last edited:
Im thinking about moving to something besides OpenMediaVault for my home server. All I really currently run on it is some containerized Deluge and Emby with SnapRaid. Ive realized that I could easily run just about any web interface... Im going to be linking it to an ai bot as soon as I rebuild it to do some of the managing/monitoring also.

Been thinking about something like whats talked about in this thread. Thoughts?
 
Question to Claude AI:
Why is my Proxmox autosnap job 1780659397 throwing an error?

I could check the logs now—the local job log in the Windows frontend, or perhaps the logs on the Proxmox member—and would probably figure out the cause even without AI. However, there are more exciting activities than analyzing log files and troubleshooting complex problems.

Response from Claude within 10 seconds: Job 1780659397 is a daily snapshot job on the rpool of member proxmox_1 (192.168.2.112). It runs Sundays at 11:00 PM with keep=2, hold=8, VM-Freeze=yes, and the additional option include=/etc/pve. It is currently failing, not because of the settings, but due to an outdated program version on the member.

I read the job files and the log.

Findings
  • Error: Today's manual run at 10:45 AM failed with flag provided but not defined: -pre-snap-cmd. Because of include=/etc/pve, the job passes the --pre-snap-cmd option to cs-freeze4snap so that /etc/pve is included in the snapshot via rsync. The cs-freeze4snap tool on the Proxmox member does not recognize this option because it is older than version 1.3.0. Your local Windows program is version 1.3.0 and recognizes it.
  • Last Success: The last successful run was on 08/30/2026 (rpool@i_daily-…), and prior to that on 06/05.
  • Missing Auto-Runs: For the Sundays of 09/20, 09/27, and 10/04, only the auto-request (request … via=auto) appears in the log, but with no start time and no result. Consequently, the snapshots for those weeks are likely missing. I cannot see from the log why the job did not start there. Even auto.log only lists the Scrub and Index jobs; the snapshot job is not listed.
  • Warning: snaplib.pl only logs a warning for versions below 1.3.0, but still passes the option anyway, which causes the run to abort hard.
How to Fix It
  1. Update the cs-freeze4snap tool on member proxmox_1 via About > CS Tools Download (select the member and click Update).
  2. Afterwards, start the job manually once and check the log.
I could have found the cause without AI in about 10 minutes, whereas a pure user might have pondered for a long time before finding the cause and simple solution. Of course, one could argue that in a cluster, all members should always be updated rather than just individual ones, or that the job could check program versions. But there are also other OS or storage problems that aren't as straightforward as this one, requiring you to read multiple log files and research where such an issue has been described before. That is precisely where AI with up-to-date data is an unbeatable helper.
 
Illumos ZFS and its derivative OpenZFS have been released for FreeBSD, Linux, and macOS. All that is really missing now for a universal NAS file system is Windows, and that is getting closer and closer.

OpenZFS 2.4.4rc4 for Windows

Release zfs-windows-2.4.4rc4 · openzfsonwindows/openzfs

*** rc4

  • Explorer integration exposing snapshot versions
  • Fix "zfs diff"
  • zfs_tray features
  • Paging IO deadlock fix
  • Fix BSOD related to SEQ
  • zfs_inactive deadlock fix
Although the new 2.4.4 rc4 for Windows is still a pre-release on the way to the latest release candidate and final release, it has now gone through quite a few fixes and tests. I hope that rc5 can become the new latest version, and—provided not too many additional programs are discovered that still have issues with ZFS—a final "Released" version will follow at some point.

Quite interesting is the ZFS snapshot integration in Windows Explorer, especially for Windows 11, since Microsoft removed VSS with ZFS snapshots as "Previous Versions" there in order to push the server versions where that feature is available.

1791632555027.png
 
Last edited:
You must log in or register to reply here.
Back
Top