<div dir="ltr"><div><div><div><div><div><div><div><div><div>fsck -n is used to verify only.<br><br></div>The touch on /forcefsck will force a regular fsck on unmounted<br></div>partitions on boot up.<br><br></div>So what I've done is:<br><br></div>fsck -n<br></div>touch /forcefsck<br></div>reboot<br><br></div>times three.<br><br></div>It should be actually fixing the problems on reboot.<br><br></div><div>I can find there are at least some fsck errors on every Redhat 6 machine,<br></div><div>whether virtual or physical. I mean I've tested the fsck -n status on about<br></div><div>twelve systems which have some errors. Only 2 showed a history<br></div><div>of SCSI errors, both happening to be VMware.<br><br></div><div>Maybe some other people can test this on their Redhat 6 systems<br></div><div>and see if fsck -n /var or similar comes back clean. You might<br></div><div>be surprised to see the same state I've noticed. There is<br></div><div>no issue like read-only file system. Everything is functional.<br></div><div><br></div><div><div><div><div><div><div><div><div><div><div><div class="gmail_extra"><br><div class="gmail_quote">On Wed, Dec 20, 2017 at 5:57 PM, Gianluca Cecchi <span dir="ltr"><<a href="mailto:gianluca.cecchi@gmail.com" target="_blank">gianluca.cecchi@gmail.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div dir="ltr"><span class=""><div class="gmail_extra"><br><div class="gmail_quote">On Wed, Dec 20, 2017 at 9:27 PM, francis picabia <span dir="ltr"><<a href="mailto:fpicabia@gmail.com" target="_blank">fpicabia@gmail.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><div dir="ltr"><div><div><div><div><br><div>With one development box I did touch /forcefsck and rebooted.<br></div><div>Retested fsck and still issues. Repeated this cycle 3 times<br></div><div>and no improvement.<br></div></div></div></div></div></div></blockquote></div></div><div class="gmail_extra"><br></div></span><div class="gmail_extra">Hi,</div><div class="gmail_extra">not going into the reasons of the problem, but into your "cycle".</div><div class="gmail_extra">if I have understood correctly your sentence, you run fsck and use "-n" option that automatically answers "no" to all the questions related to problems and suggestions to fix them.</div><div class="gmail_extra">So, as you didn't fix anything, the next run the fsck command exposes the same problems again....</div><div class="gmail_extra"><br></div><div class="gmail_extra">Sometimes I have seen in vSphere environments storage problems causing linux VMs problems and so kernel to automatically put one or more filesystems in read-only mode: typically the filesystems where there were writes in action during the problem occurrence.</div><div class="gmail_extra">So in your case it could be something similar with impact to all the VMs insisting on the problematic storage / datastore<br></div><div class="gmail_extra">If you have no monitoring in place, such as Nagios and a monitor like this:</div><div class="gmail_extra"><a href="https://exchange.nagios.org/directory/Plugins/Operating-Systems/Linux/check_ro_mounts/details" target="_blank">https://exchange.nagios.org/<wbr>directory/Plugins/Operating-<wbr>Systems/Linux/check_ro_mounts/<wbr>details</a></div><div class="gmail_extra">you can go ahead also some days before realizing that you had a problem</div><div class="gmail_extra">Analyzing /var/log/messages you should see when it happened<br></div><div class="gmail_extra"><br></div><div class="gmail_extra">Take in mind that if the filesystem went in read-only mode due to a SCSI error (action taken by the kernel to prevent further errors and data corruption), you will not be able to remount it read-write, but you have to reboot the server.</div><div class="gmail_extra"><br></div><div class="gmail_extra">Just a guess.</div><div class="gmail_extra">HIH,</div><div class="gmail_extra">Gianluca</div><div class="gmail_extra"><br></div></div>
<br>______________________________<wbr>_________________<br>
rhelv6-list mailing list<br>
<a href="mailto:rhelv6-list@redhat.com">rhelv6-list@redhat.com</a><br>
<a href="https://www.redhat.com/mailman/listinfo/rhelv6-list" rel="noreferrer" target="_blank">https://www.redhat.com/<wbr>mailman/listinfo/rhelv6-list</a><br></blockquote></div><br></div></div></div></div></div></div></div></div></div></div></div></div>