darshin 0 Newbie Poster

KQ Infotech Pvt. Ltd. is a globally focused software development and consulting firm headquartered in Pune, India, with core expertise in the field of systems and storage. Being a pure technology company, KQ believes in applying innovation to evolving technologies, the resultant of which is some highly ground-breaking products like ZFS port to Linux. We are also due in coming up with our products in the field of virtualization.

KQ’s expertise in kernel programming and deep understanding of file systems has enabled it to take up the task of porting ZFS to Linux for the open source community. After dedicated effort, we have finally reached the beta stage of the port and are now making the much awaited and discussed code available for the selected beta customers. Please log on to the website zfs.kqinfotech.com to apply and register yourself through the beta form in order to get the code for testing. Once you fill the form, one of our representatives will be contacting you to assist you with the proceedings and arrange an interactive one on one demo with our ZFS expert.

As we are selecting a batch of 25 beta customers from different testing environments, please await your turn. To allow proper support bandwidth for beta customers, we have limited the batch to 25. We would be increasing the bandwidth as and by the beta matures. We are in the process of selecting our first batch of customers, so please register yourself through the form now.

Thank you all for your continued support and interest.

Dani AI

Generated

Regarding 's announcement, the following practical notes help anyone who will be testing a new ZFS implementation on Linux. They focus on legal risk, safe test practices, what to measure, and what to include in bug reports.

ZFS licensing can affect how the code is distributed and used. The ZFS codebase is under the CDDL; the kernel uses GPLv2. Review the license texts (CDDL 1.0, GPLv2) and, where redistribution or packaging is involved, get legal guidance rather than assuming compatibility.

A short safety and test checklist:

  • Never start on production data. Use fresh disks, snapshots or disposable VMs and keep full backups.
  • Exercise pool operations: create/destroy pools, replace devices, simulate device loss, and run scrubs/resilver cycles to watch for checksum or metadata failures.
  • Stress with mixed workloads (large sequential, random IOPS, metadata-heavy) and benchmark with tools such as fio.
  • Test upgrade/rollback paths and interaction with existing stack components (LVM, dm-crypt, RAID controllers).

Kernel-version and packaging notes:

  • Filesystem and kernel APIs change. Verify which kernel versions are supported and how the module is delivered (out-of-tree module vs DKMS vs in-tree). See the kernel driver API docs (kernel.org driver API) and packaging options like DKMS.

When filing issues, include: distro and exact kernel version, ZFS/module version, hardware details, precise reproduction steps, dmesg/journalctl output, and the ZFS admin outputs (pool and dataset status). Point maintainers to the upstream source if relevant (for example, OpenZFS on GitHub).

If there is any doubt about production use or redistribution, err on the side of caution and consult legal counsel or upstream maintainers before proceeding.

Be a part of the DaniWeb community

We're a friendly, industry-focused community of developers, IT pros, digital marketers, and technology enthusiasts meeting, networking, learning, and sharing knowledge.