From: Ian Zapczynski (ianz@quarterleaf.com)
Date: Thu Sep 26 2002 - 11:16:40 EDT
Hello all,
You've probably heard this one before. When I attempted to create a
Jumpstart server with my Solaris 8 10/01 CD on an E250, I received a
"file table overflow" message and found a suggestion in the archives to
add the following to /etc/system and reboot:
set hsfs:nhsnode=4096
I have done that, and now I get just the error "ERROR: Copy of CD image
failed" near the end of the process, and the following is in
/var/adm/messages:
Sep 26 10:56:34 myhost hsfs: [ID 450429 kern.notice] NOTICE: hsfs:
hsnode table full, 4096 nodes allocated,
Sep 26 10:56:34 myhost hsfs: [ID 111760 kern.notice] hsfs: consider
increasing # of hsnodes using
Sep 26 10:56:34 myhost hsfs: [ID 806515 kern.notice] hsfs: 'set
hsfs:nhsnode=num' in /etc/system
Sep 26 10:56:34 myhost hsfs: [ID 858973 kern.notice] hsfs: and
rebooting.
My concern is that I already scheduled a reboot of this server once
(they won't let me do it doing business hours), so can I feel confident
that if I increase this number to 8192 or even higher, things will
finally go smoothly? If I understand what this setting does properly, I
am assuming that since no other file systems on this unit are mounted as
hsfs, setting this number "too high" won't cause any adverse problems.
Am I correct?
Any thoughts or suggestions would be most appreciated! I'm hoping that
after making a similar change tonight I'll actually be able to soon
Jumpstart my Netra T1.
_______________________________________________
sunmanagers mailing list
sunmanagers@sunmanagers.org
http://www.sunmanagers.org/mailman/listinfo/sunmanagers
This archive was generated by hypermail 2.1.7 : Wed Apr 09 2008 - 23:24:59 EDT