Matthew,
Another idea is to have a cronjob touch /forcefsck on all the servers.
This should force a fsck on the next reboot. It would be pretty simple
to either have a cronjob that verifies and creates the file if it is
missing or use something like puppet.
cheers,
ski
On 10/29/2013 12:51 PM, Mathew Snyder wrote:
I agree. Others have mentioned this as well.
I just need to work out how to ensure that fsck is performed after EVERY
reboot so we can ensure this is corrected when it happens rather than
logging in and running tune2fs on each one. I suppose a cron'ed script
that checks the state of the filesystem and forces a fsck if any are in
read-only mode when they shouldn't be would be a start.
If there is a method to configure the OS to do this without a script
that would be ideal. We'd prefer just flipping a setting that tells the
OS to run a fsck on reboot whether the filesystem is clean or dirty.
-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:45 PM, John Stoffel <j...@stoffel.org
<mailto:j...@stoffel.org>> wrote:
Hi Mathew,
One question I have is why don't your 1400 servers just do filesystem
checks on reboot then? Since you have to stop them and reboot them,
what's wrong with letting the OS do the work? This should be more
scriptable than having to manually boot into a recovery setup.
Do you have the data stored on the VMs? It might be quicker to just
rebuild the VMs from known good configs and then get them running
again.
Honestly, if you're going to reboot them anyway (probably by a hard
reset, try letting the redhat OS do the filesystem checks on reboot
instead.
John
_______________________________________________
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/
--
"When we try to pick out anything by itself, we find it
connected to the entire universe" John Muir
Chris "Ski" Kacoroski, Director of LOPSA, s...@lopsa.org,
206-501-9803 or ski98033 on most IM services
_______________________________________________
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/
