I'm actually on a call right now and the use of forced fsck on reboot has been brought up. However, in my experience this is a one-time event and after reboot the "forced" file that makes it happen is removed.
I suppose I need to ensure this file is persistent. -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 12:11 PM, Mark Plaksin <ha...@usg.edu> wrote: > Mathew Snyder <mathew.sny...@gmail.com> writes: > > > How do your systems handle it? When the storage suddenly disappears and > then reappears the OS isn't seeing that as an event that requires an > automatic, online fsck. > > When the OS or filesystem(s) lose their mind due to such an event we've > (in general) found no successful recourse other than rebooting. And the > fscks that happen at boot do the trick. > > Such events are rare for us but not unheard of. >
_______________________________________________ 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/
