I'm looking at information for the onerror=panic option. What happens when I cause a kernel panic besides the system essentially becoming inoperable? Does it automatically force a fsck on the next reboot? So far, everything I've seen indicates that it simply creates a crash dump. That really isn't all that useful in this situation as we know what causes the problem.
-Mathew "When you do things right, people won't be sure you've done anything at all." - God; Futurama "We'll get along much better once you accept that you're wrong and neither am I." - Me On Tue, Oct 29, 2013 at 3:52 PM, Jonathan <lo...@redigloo.org> wrote: > Hi, > > There have been a few suggestions around "touch /forcefsck" and passing > flags to shutdown. But these don't work after the SAN horse has bolted and > the file system is read-only. Since a system with a read-only disk is > generally unusable, as part of our build procedures we change the fstab > mount option from onerror=readonly to onerror=panic. In the event of a SAN > error, affected VMs reboot and because the file system wasn't cleanly > unmounted, it gets checked on the way back up. This is all just sticking > plaster, of course, but at least it's automatic. > > Jonathan. >
_______________________________________________ Tech mailing list Tech@lists.lopsa.org https://lists.lopsa.org/cgi-bin/mailman/listinfo/tech This list provided by the League of Professional System Administrators http://lopsa.org/
