In theory, yes. However, this has proven to not be the case. Sure, fsck runs, but it does not repair the filesystem. Instead it tells us to run the check manually from an offline state (ie. Rescue mode).
My goal is to eliminate this need through one of the methods I listed earlier. Hopefully it is simply a matter of finding a practical way to pass the -y option as that seems to be the crux of all this. On Oct 30, 2013 4:18 PM, "Edward Ned Harvey (lopser)" <lop...@nedharvey.com> wrote: > > From: Mathew Snyder [mailto:mathew.sny...@gmail.com] > > > > I understand what you're saying. I wonder if perhaps, though, the > disconnect > > between your statements and that of Brandon's is the fact that this > isn't a > > standard "crash". This is a situation in which the drives just go > "POOF". Not > > something common, but certainly not unheard of. > > When the drives go poof, the kernel may stay alive a while longer, but as > no more writes (or reads) are possible, you eventually power off the > machine, and the disk state is left exactly as if the power to the whole > system had been cut, rather than just the communication bus. Later, you > reconnect the drives and boot the system, and it appears exactly as if > recovering from any other ungraceful reboot. So from that perspective, the > crash you experience is as standard as standard can get. >
_______________________________________________ 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/
