I've not been overly impressed with my interactions with RedHat support, but since you are already paying for the support I would file a ticket with them to see if they have any best practices they would recommend (and then share that info with the mailing list).
On Tue, Oct 29, 2013 at 3:55 PM, matthewhall <matthewh...@plfc.org.uk>wrote: > Hugely speculating - I guess you could do it by calling tune2fs to > override the number of mounts before another fsck? > > http://linux.die.net/man/8/**tune2fs <http://linux.die.net/man/8/tune2fs> > > Not a particularly pretty solution ;-) > > > > On 29.10.2013 19:51, 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 croned >> >> script that checks the state of the filesystem and forces a fsck if >> any are in read-only mode when they shouldnt be would be a start. >> >> >> If there is a method to configure the OS to do this without a script >> that would be ideal. Wed 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 wont be sure youve done anything at >> all." - God; Futurama >> >> "Well get along much better once you accept that youre wrong and >> >> neither am I." - Me >> >> On Tue, Oct 29, 2013 at 12:45 PM, John Stoffel <j...@stoffel.org> wrote: >> >> Hi Mathew, >>> >>> One question I have is why dont your 1400 servers just do filesystem >>> >>> checks on reboot then? Since you have to stop them and reboot them, >>> whats 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 youre 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<https://lists.lopsa.org/cgi-bin/mailman/listinfo/tech> >> This list provided by the League of Professional System Administrators >> http://lopsa.org/ >> > ______________________________**_________________ > Tech mailing list > Tech@lists.lopsa.org > https://lists.lopsa.org/cgi-**bin/mailman/listinfo/tech<https://lists.lopsa.org/cgi-bin/mailman/listinfo/tech> > This list provided by the League of Professional System Administrators > http://lopsa.org/ >
_______________________________________________ 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/
