4.0.0 HP Polyserve Matrix Server Release Notes (T5392-96051, March 2010)

• Case-insensitive naming.
• Case-sensitive naming.
• Content indexing. PSFS support is the same as the FAT filesystem. (See “Unsupported Features”
for more information.)
• Directory Change Notification (DCN). PSFS supports both local-node and cross-node Change
Notification.
• Disk quotas.
• 8.3 short file names and name tunneling.
• Hidden, readonly, archive bits (and so on).
• Memory-mapped files. PSFS support is for the local node only; memory mapped file data is not
coherent cluster-wide. Memory-mapped sparse files are not supported. (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:
• File encryption and compression. This behavior is consistent with the FAT filesystem.
• Hard links.
• System ACLs and filesystem auditing.
• NTFS change journal. As a consequence, file replication services (FRS) cannot be used. Content
indexing is also affected. The content indexing service uses the NTFS change journal to determine
when to update the indices. In the PSFS filesystem, updates to the indices are done less frequently.
• Object IDs.
• Online defragmentation.
• Memory-mapped sparse files.
• Other filesystems (PSFS or non-PSFS) cannot be mounted on mount points within PSFS filesystems.
• Pagefiles such as pagefile.sys cannot be placed on a PSFS filesystem.
• Removable media.
• Use as the boot filesystem.
4