HP Clustered FileSystem3.6.1 for Windows release notes (T4422-96003, September 2008)

• Alternate Data Streams (ADS).
• Byte-range locking. PSFS supports both local-node and cross-node byte-range
locking.
• Cached and non-cached file access.
• 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 (D CN). 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
theWindows cachemanager.
• Remo vable devices.
• Reparse p oints. 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.
Fil
esystem implementation differences
Alt
hough the PSFS filesystem is a standard Windows filesystem and supports standard
fil
esystem 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:
8