Review infra-raidmismatch SOP

Signed-off-by: Michal Konečný <mkonecny@redhat.com>
This commit is contained in:
Michal Konečný 2021-09-02 15:12:52 +02:00
parent 8d66f2e477
commit df7cb54128
2 changed files with 7 additions and 14 deletions

View file

@ -50,7 +50,7 @@
** xref:hotness.adoc[The New Hotness - SOP]
** xref:infra-git-repo.adoc[Infrastructure Git Repos - SOP]
** xref:infra-hostrename.adoc[Infrastructure Host Rename - SOP]
** xref:infra-raidmismatch.adoc[infra-raidmismatch - SOP in review ]
** xref:infra-raidmismatch.adoc[Infrastructure Raid Mismatch Count - SOP]
** xref:infra-repo.adoc[infra-repo - SOP in review ]
** xref:infra-retiremachine.adoc[infra-retiremachine - SOP in review ]
** xref:ipsilon.adoc[ipsilon - SOP in review ]

View file

@ -1,19 +1,12 @@
= Infrastructure/SOP/Raid Mismatch Count
= Infrastructure Raid Mismatch Count SOP
What to do when a raid device has a mismatch count
== Contents
[arabic]
. Contact Information
. Description
. Correction
____
[arabic]
. Step 1
. Step 2
____
* <<_contact_information>>
* <<_description>>
* <<_correction>>
== Contact Information
@ -45,7 +38,7 @@ the directions below.
More than anything these steps are to A) Verify there is no problem and
B) make the error go away. If step 1 and step 2 don't correct the
problems, PROCEED WITH CAUTION. The steps below, however, should be
problems, *PROCEED WITH CAUTION*. The steps below, however, should be
relatively safe.
Issue a repair (replace mdX with the questionable raid device):
@ -62,7 +55,7 @@ cat /proc/mdstat
....
Issue a check. It's this check that will reset the mismatch count if
there are no problems. Again replace mdX with your actual raid device.:
there are no problems. Again replace mdX with your actual raid device:
....
echo check > /sys/block/mdX/md/sync_action