3.6.0 Matrix Server Release Notes (5697-7087, February 2008)

PolyServe Matrix Server Release Notes 4

• Memory-mapped files. PSFS support is for the local node only;

memory mapped file data is not coherent cluster-wide. (See

“Filesystem Semantics” for more information.)

• Open by File ID.

• Opportunistic locking. PSFS supports coherency of client-cached data

over a single CIFS server and over multiple CIFS servers sharing the

same filesystem.

• Paging I/O. This is reads and writes initiated by the memory manager,

in which it asks the filesystem to fetch or store pages of file contents.

Some examples are reads from files being executed and reads and

writes to files cached by the Windows cache manager.

•Removable devices.

• Reparse points. PSFS filesystems can be mounted on mount points

residing on NTFS filesystems.

• Security descriptors. Security updates are immediately and

simultaneously applicable to all servers in the cluster. Note that

System ACLs and filesystem auditing are not supported.

• Sparse file API.

•Unicode file names.

Filesystem Implementation Differences

Although the PSFS filesystem is a standard Windows filesystem and

supports standard filesystem operations, it differs from the NTFS

filesystem in certain areas. Also, certain Windows utilities and

applications cannot manipulate a PSFS filesystem in the same manner as

an NTFS filesystem.

Unsupported Features

The following NTFS features are not supported on PSFS filesystems:

• Alternate data streams. This behavior is consistent with the FAT

filesystem. Applications will typically discard any alternate data

streams such as summary properties.