This is an update rollup for the Single Instance Storage (SIS) component in Windows Storage Server 2008 R2. This update rollup resolves the following issues:
Issue 1
When data is written to a file which resides on a SIS volume of a remote server and an application on the remote server reads the file by using file mapping, the new data may be lost. An antivirus application is an example application which may read files locally by using file mapping.
Issue 2
When a file is compressed or decompressed on a SIS volume and the file was previously changed and the modification was interrupted or failed, the file may be corrupted.
Issue 3
After a file is truncated to empty size on a SIS volume by using the CreateFile function together with the TRUNCATE_EXISTING creation disposition:
Issue 4
When a file is opened on a SIS volume that uses file system transaction and the file is compressed by using NTFS compression, the file may be corrupted.
Important
Windows Storage Server products are OEM-only products. OEMs must set up a contract with Microsoft Licensing through their OEM account managers before the OEMs can access update packages for Windows Storage Server. This update rollup is distributed only through Microsoft OEM Online. Send questions about this update package to the following email address:
Issue 1
When data is written to a file which resides on a SIS volume of a remote server and an application on the remote server reads the file by using file mapping, the new data may be lost. An antivirus application is an example application which may read files locally by using file mapping.
Issue 2
When a file is compressed or decompressed on a SIS volume and the file was previously changed and the modification was interrupted or failed, the file may be corrupted.
Issue 3
After a file is truncated to empty size on a SIS volume by using the CreateFile function together with the TRUNCATE_EXISTING creation disposition:
- If the file is read without reopening it, the system may return data as if the file was not truncated. For example, consider a situation where the original file is 2 megabytes (MB) and is opened by using the CreateFile function together with the TRUNCATE_EXISTING creation disposition. When the first 1 MB is read, the system may return the original 1 MB of content even though the file size is zero.
- If the file is written without reopening it, the system may behave as if the file was not truncated. For example, consider a situation where the original file is 2 MB and is opened by using the CreateFile function together with the TRUNCATE_EXISTING creation disposition. When the first 1 MB is written with new data, the new file may be 2 MB with the first 1 MB of new data and second 1 MB of original data.
Issue 4
When a file is opened on a SIS volume that uses file system transaction and the file is compressed by using NTFS compression, the file may be corrupted.
Important
Windows Storage Server products are OEM-only products. OEMs must set up a contract with Microsoft Licensing through their OEM account managers before the OEMs can access update packages for Windows Storage Server. This update rollup is distributed only through Microsoft OEM Online. Send questions about this update package to the following email address: