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

• 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 r eplication 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
PSF S filesystems.
• Pagefiles such as pagefile.sys cannot be placed on a PSFS filesystem.
• Removable media.
• Use as the boot filesystem.
• The following Disk and File Management features provided in Windows 2003
R2: File Server Management, Microsoft Services for N etwork File System, File
Server Resource Ma nager.
• The Active Directory features provided in Windows 200 3 R2.
If you restore data from an NTFS filesystem to a PSFS filesystem, you may see warnings
such as the following. The warnings indicate that data belonging to an unsupported
NTFS featurewillbelostduringthe restore.
Warning: The target file system does not support some of the
features of the original filesystem. Some data may not be
restored as a result.
Filesystem semantics
The PSF
S
filesystem differs semantically from the NTFS filesystem in the following ways:
• A file cannot be deleted if it i s currently open on another node.
• A file cannot be “renamed over” if it is currently open on another node. For
examp
le, an attempt to rename filea to fileb will fail if fileb is currently
open on another
node.
• Thetimethata file was last accessed is not updated after a successful read
oper
ation, even on the local node.
• When a directory is renamed, subsequent change notify requests within that
director y are not c ompleted. For example, if Windows Explorer is open at a
certain directory on the local node and that directory is renamed on a remote
nod
e, any subsequent changes to the renamed d irector y will not appear in
HP Clustered File S ystem 3.6 .1 f or Windows
9