Fujitsu SPARC Enterprise M3000 Catatan Produk - Halaman 34
Jelajahi secara online atau unduh pdf Catatan Produk untuk Server Fujitsu SPARC Enterprise M3000. Fujitsu SPARC Enterprise M3000 42 halaman.
Juga untuk Fujitsu SPARC Enterprise M3000: Panduan Memulai (8 halaman), Catatan Produk (38 halaman), Manual Keselamatan dan Kepatuhan (34 halaman)
Solaris OS Issues and Workarounds
This section contains information about Solaris OS issues.
and
TABLE 10
release you are using.
Solaris OS Issues and Workarounds for All
Supported Releases
TABLE 7
Solaris OS.
Solaris OS Issues and Workarounds for All Supported Releases
TABLE 7
CR ID
Description
6481002
Installing the Solaris OS from the network
using certain PCI-Express cards may cause a
panic.
6519290
Large amounts of I/O on swap devices can
cause the system to appear hung by
overwhelming the I/O system. The amount of
I/O required can be generated through a
number of ways, eg memory shortage, heavy
use of /tmp etc.
6531036
The error message network
initialization failed appears
repeatedly after a boot net installation.
6532215
volfs or dscp service may fail when domain is
booted.
svc:/platform/sun4u/dscp:default:
Method "/lib/svc/method/svc-dscp
start" failed with exit status 95.
svc:/system/filesystem/volfs:defaul
t: Method or service exit timed
out. Killing contract 59.
24
SPARC Enterprise M3000 Server Product Notes for XCP Version 1093 • July 2010
list issues you might encounter, depending upon which Solaris OS
lists Solaris OS issues that you might encounter in any supported release of
TABLE 7
Workaround
If you are using a Sun PCI-E Dual Gigabit
Ethernet Adapter MMF card or a Sun PCI-E
Dual Gigabit Ethernet Adapter UTP card, do
not install the Solaris using either of these
cards. Instead, use other network devices, such
as the onboard Gigabit Ethernet or another
network device.
Set the following to /etc/system and then
reboot the domain:
set maxfastscan=0x2000
No workaround is available.
This message can be safely ignored.
Restart the service if the failure is observed. To
avoid the problem, issue the following
commands.
# svccfg -s dscp setprop
start/timeout_seconds=count: 300
# svccfg -s volfs setprop
start/timeout_seconds=count: 300
# svcadm refresh dscp
# svcadm refresh volfs
,
,
TABLE 8
TABLE 9