From: Dave K (davek08054@gmail.com)
Date: Mon Jun 11 2007 - 15:19:38 EDT
I need to prepare some sort of guidelines for $WORK's customers on the
topic "Minimizing Operator Intervention Following Unplanned Power
Interruption". This is for Solaris 8, 9, and/or 10 running on SunFire
and/or Netra 120, 210, and 240 systems.
I know the obvious steps, such as ensuring that the LOM/ALOM is
configured to automatically power on the system and that the OpenBoot
environment is configured to automatically boot the OS. We already
have UFS logging enabled for all filesystems.
There was a item here back in 2000: "automatic fsck -y at boot?":
http://www.sunmanagers.org/archives/2000/1429.html
I'm wondering if we should be implementing this, as even with logging
enabled we still see cases where single-user mode and subsequent
manual fsck is required.
I know we could avoid other disk issues by switching to "sync" mode,
and otherwise disabling write buffering, but I don't think we can
accept the performance hit.
Are there other things that can be done to avoid single-user mode at boot?
Note: I know the right answer is to eliminate unplanned power
interruptions in the first place, but they are inevitable. Stupid
user tricks can readily defeat even the best power systems.
Note 2: Surprisingly, while Google returns a lot of hits as to what to
do in single user mode, it doesn't return much about avoiding it in
the first place.
Note 3: An update to the automatic fsck article. It looks like in
Solaris 10 you need to edit /lib/svc/share/fs_include.sh,
/sbin/mountall, and /usr/sbin/mountall to change the fsck options.
-- Dave K Unix Systems & Network Administrator Mount Laurel NJ _______________________________________________ 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:42:03 EDT