Microsoft Windows Storage Server 2003
This section describes issues related to Microsoft Windows Storage Server 2003.
Windows Storage Server 2003
Issue:
When repeatedly copying a
fi
le from a Linux client to an HP NAS Server running Windows
Storage Server 2003, the NAS server may stop responding (hang)
Description
The server becomes unresponsive because
QAFilter.sys
causes a deadlock
in the NTFS
fi
le system by incorrectly making a blocking call from a completion
routine. This issue occurs if you are using a version of
QAFilter.sys
that
is earlier than version 5.30.2190.7.
Workaround
Contact HP Support to get the following Storage Manager
fi
x updates:
QFE907648 and QFE906194.
Issue:
Quotas used
Description
If
fi
les for user accounts are deleted using the Local Login account, this has the
effect of moving user
fi
les to the recycle bin instead of removing them from the
drive. Due to the nature of volume--based quotas (instead of directory-based) this
has the effect of not releasing quota space.
Workaround
Delete
fi
les from the Recycler and/or remove the recycle bin from the data drives.
Issue:
Blue screen condition occurs when using Microsoft Windows Server 2003 SP1 with StorageWorks
NAS and ProLiant Storage Server products
Description
Microsoft has offered Windows Server 2003 Service Pack 1 (SP1). If SP1 is
installed directly without Service Release 5.6 or the system patch provided in the
previous Service Release (SR5.5), a blue screen condition occurs when the HP
NAS server is restarted after the SP1 installation. At that point, the NAS server
no longer operates. The following customer bulletin contains further details and
affected products:
http://h20000.www2.hp.com/bizsupport/TechSupport/
Document.jsp?objectID=PSD_CB0204W
Workaround
HP highly recommends that you install Windows Server 2003 SP1 using
the SR5.6 software. To learn more and order the Service Release, go to
http://software.hp.com
, and select the
Storage and NAS
link under
Product
Category
. Select the
HP Storage Server Service Release
link for more information
about updates and enhancements.
Issue:
Bugcheck 0x50 (PAGE_FAULT_IN_NONPAGED_AREA) in next boot after disabling Multipath
Support
Description
Using the Microsoft Device Manager to disable the HP MPIO driver and rebooting
the system causes the system to continuously reboot. After successfully installing
the MPIO and DSM for MSA/EVA/XP, right-click and disable Multipath Support
from Device Manager and reboot the system. During the next boot, the system
bugchecks with bugcheck code 0x50 when coming up. The issue occurs because
the DSM uses MPIO export DsmGetVersion. This call is made even before
the DSM registers with MPIO. Since MPIO is disabled, DsmGetVersion is not
available, and the system bugchecks. The uninstall driver selection under Device
Manager works
fi
ne.
Workaround
Bring up the Safe Mode menu using
F8
during the reboot sequence. Select
Last
Known Good Con
fi
guration
to recover the system, or boot into recovery console
and disable the DSM service.
Issue:
Incorrect error when
fi
le screening is implemented under Storage Manager
34
Содержание StorageWorks X5000
Страница 2: ......