4.1.0 HP Polyserve Matrix Server Release Notes (T5392-96068, October 2010)

Warning: Unable to set the short 8.3 name for “V:\test-restore\WINNT\q50.dmp.gz”.
Reason: The parameter is incorrect.
Filesystem semantics
The PSFS filesystem differs semantically from the NTFS filesystem in the following ways:
• A file cannot be deleted if it is currently open on another node.
• A file cannot be “renamed over” if it is currently open on another node. For example, an attempt
to rename filea to fileb will fail if fileb is currently open on another node.
• The time that a file was last accessed is not updated after a successful read operation, even on
the local node.
• When a directory is renamed, subsequent change notify requests within that directory are not
completed. For example, if Windows Explorer is open at a certain directory on the local node
and that directory is renamed on a remote node, any subsequent changes to the renamed directory
will not appear in the local Explorer window. You will need to close and reopen Explorer to see
the renamed directory.
• Memory-mapped files are not coherent across nodes. Because PSFS is a shared filesystem, the
same file can be mapped into memory on more than one node. When a change is made to a file
on a remote node, the local node does not see the change immediately. This occurs because the
operating system on the remote node may not immediately write the change to disk. Consequently,
PSFS allows writes to files that are being executed on other nodes.
• If the Bypass Traverse Checking privilege is not enabled, differences in traverse access checking
for Directory Change Notification (DCN) may be observed. On NTFS, before a change notify
request is completed, an access check is performed to determine whether the subscriber has traverse
access to the directory in which the contents were modified. If the subscriber does not have traverse
access, the change notification will not be delivered.
On PSFS, this check is not performed and the contents of directories (e.g., the names of files) may
be exposed via DCN to a user who would otherwise not obtain this data. Traverse access checking
other than during directory change notification is as expected, so access to file contents is not
compromised. The user is advised not to depend on traverse access checking to protect sensitive
data that is encoded in the names of files or directories. Instead, the user should place sensitive
data in files and should rely on file security descriptors to deny access to the files' contents by
unauthorized users.
• On NTFS, a change to an long file name (LFN) results in a change notification using the LFN, and
a change to a short file name (SFN) results in a change notification using the SFN. On PSFS, the
change notification can use either the LFN or SFN in either case.
• PSFS does not support direct renaming of an unnamed primary stream to Alternate Data Streams
(ADS). PSFS does support copying an unnamed primary stream to ADS.
• With PSFS, a file cannot be renamed or deleted, either locally or remotely, if any of its Alternate
Data Streams (ADS) are still open (with or without SHARE_DELETE).
Compatibility support for Hyper-V
A supported guest OS can be installed on any node in the cluster. VHD and VM state (VSV, BIN) can
be hosted on a PSFS filesystem and VHD, VSV and BIN state files can be stored on the filesystem.
The supported guest operating systems are:
• Windows 2008 32-bit and 64-bit guest OS
• Vista 32-bit and 64-bit (with SP1) guest OS
• Windows 2003 (with SP2) 32-bit and 64-bit guest OS
• Windows 2000 (with SP4) 32-bit guest OS
HP PolyServe Matrix Server 4.1.0 release notes 5