To access the image to view or install you will need to enter the following 
command as a root user on a linux system:

mount <path_to/image.img> <mount_point> -t iso9660 -o loop

This command will mount the image as an iso9660 file system via the loop 
device.


IMPORTANCE NOTICE: All SIOS SIOS Protection Suite for Linux Customers using DataKeeper for Linux

Subject: Important Notice: Kernel issue with SIOS DataKeeper for Linux

Dear SIOS Protection Suite for Linux Customer:

As our valued customer, we want to proactively notify you of an issue that we discovered in the md/raid1 kernel module of several Linux releases. 

Due to this issue, a partial resync of data within supported versions (v9.3.2 - v9.5.1) of SIOS Protection Suite for Linux with DataKeeper 
cluster nodes may NOT resync all blocks. The following table shows the affected distributions and kernel versions:

Distribution            Affected Kernels        Supported SPS-L versions for the Distribution at Left
RHEL/CentOS/OEL 8.2         All                     SPS-L v9.5.1
RHEL 8.3                    All                     SPS-L v9.5.1
SLES 12 SP4             >= 4.12.14-95.51            SPS-L v9.3.2 - v9.5.1
SLES 12 SP5             >= 4.12.14-122.20           SPS-L v9.5.0 - v9.5.1
SLES 15 SP1             >= 4.12.14-197.37.1         SPS-L v9.4.1 - v9.5.1
SLES 15 SP2                 All                     SPS-L v9.5.1
OEL 7.x UEK 5           >= 4.14.35-2025.400.8 (U4)  SPS-L v9.4.0 - v9.5.1

Precautions to take immediately

SIOS has created a kernel module patch that will provide a short-term solution to this issue and we are currently testing it. 
We will make this patch available as soon as possible and we recommend customers apply it at their earliest convenience. 
We will provide the availability date for this kernel patch on May 10. In the meantime, we recommend that you take the 
following precautions immediately:

1. Do not pause the mirror. 

2. Avoid partial resyncs as much as possible

3. Initiate a full resync after any partial resyncs, reboots of the target node, or switchover/failover from primary to target
    OPTIONALLY: Consider disabling automated failover and switchover for each node.  
	
4. When stopping replication to the target, we recommend taking the application out of service on the primary until the target is restarted

5. Continue to take frequent backups of your data



For the long-term solution, SIOS has reported the issue and provided the fix to the Linux open source community and the fix has been accepted
by the Kernel Maintainer. In the future, should each OS vendor choose to implement that fix, SIOS will provide a method to return to using 
the OS vendor-released kernel module at that time. 


We strongly recommend that you take steps listed above to restore proper operation and/or prevent the issue from arising, 
or contact SIOS Support immediately to determine whether you are affected. 

If you have any additional questions, please reach out to your SIOS Technical Support or your SIOS Sales Representative so that we can help understand whether you may 
be affected by this issue. 

We are committed to the quality of our products and above all, to you, our valued customer. 

We will continue to keep you informed and we assure you that we always strive to provide you with the exceptional 
level of service you expect from SIOS Technology Corp.