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

from this service. If you do not need the Remote Stora ge Service, it can be
disabled in the Services Control Panel applet.
Windows applicat
ions
You may notice the following differences from NT FS filesystems when running
applications on PSFS filesystems:
• Cer tain Windows
applications will disable NTFS-related features when run on a
PSF S filesystem. For example, older versions of Robocopy will not c opy security
descriptors. (As a workaround, use Xcopy to copy the security descriptors.)
Open issues and workarounds
The following open issues affect HP Clustered File System and HP Clustered File System
FS
Option for Windows.
HP Clustere d
File System
Issue
3636
3793
4301
Description
Network interfaces are marked “Up” and then “Down” repeatedly
The status of network interfaces may change between “Up” and “Down” about
every five seconds when there is only one server in the cluster a nd no other IP
addressisavailable to ping. Thissituation can occur when atwo-nodecluster
losesanode or thenodeisremoved from service.
The problem appears only if the only gateway address to ping is the interface
IP address (that is, there is not a route to an outside network). This scenario is
unlikely to occur in practice, as there will likely be many clients connected to the
clusteredservervia aclient network.
However, the problem can occur in laboratory or test conditions. To avoid the
problem, add a router to the PAN network.
Managem
ent
Console does not display filesystems created when HP Clustered
File Sys
tem
was not running
If HP ClusteredFileSystemisnot runningwhile aPSFS filesystem is created with
the
psf
sformat -f
command, the filesystem will not be displayed on the HP
Manag
ement Console.
Workaround. Start the HP Clustered File System service before creating the
filesy
stem.
Filesystem mounts may disappear temporarily while a node is booting
While a node in the cluster is booting, the HP Management Console can show
filesystem mounts disappearing and then reappearing on other nodes. This is an
artifact of the cluster responding to a new node joining the cluster and causes
no
harm.
HP Clustered File S ystem 3.6 .1 f or Windows
11