Re: Starting and stopping RAID doesn't work from Cron

[Doug H.]

On Tue, 2020-06-23 at 17:07 +0100, Patrick O'Callaghan wrote:
>  On Tue, 2020-06-23 at 06:12 -0500, Roger Heflin wrote:
>  > How are you mounting the filesystem? (I don't remember details from
>  > 
>  > the prior discussion)  Directly with /dev/mdXXX or are you using
>  > some
>  > other link?  If you are using some other link then udev needs time
>  > to
>  > get the original mdXXX creation event and then create other links
>  > pointing to mdXXX.
>  > 
>  > 
>  > 
>  
>  As I said earlier, it's being mounted via /etc/fstab thus:
>  
>  UUID=6cb66da2-147a-4f3c-a513-
>  36f6164ab581       /raid                   ext4    rw,noauto,user  1
>  1
>  
>  where the script does:
>  
>                  up)     mounted && exit 0
>                          echo "- - -" > $SCAN
>                          echo -n "raid attempt: " >> $LOG
>                          for i in 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15;
>  do        # Wait up to 30 seconds
>                                  sleep 2
>                                  echo -n $i " " >> $LOG
>                                  raidon && break
>                          done
>                          raidon || (echo -n " failed:"; date; exit
>  2)            # RAID timed out
>                          (echo; echo -n "up:   "; date) >> $LOG
>                          mount /raid > /dev/null 2>&1
>                          mounted || (echo "mount failed"; exit
>  3)                # Mount failed
>  
>  and 'raidon' is defined as:
>  
>  function raidon() {     # RAID drive is running
>          if mdadm --query $RAID > /dev/null 2>&1 ; then
>                  return 0
>          fi
>          return 1
>  }
>  
>  I'm assuming that once mdadm returns 0 the array is up and running.  
Perhaps a simpler way to assure that it is running is to check a static
file that you place on the raid. If it is there then the raid is up. It
would show the file as long as it is running, even if it is degraded.

If you want to be sure that it is running non-degraded then maybe look
for "[UU]" in /proc/mdstat, assuming you just have a single RAID 1.


>  If
>  that's not the case, then it would explain the issue.
>  
>  As can be seen, it's also doing a lot of logging. I can change it to
>  run everything as a single script, but I don't really see what
>  difference it will make. I'll report back on the results.
>  
>  poc
>  _______________________________________________
>  users mailing list -- users(a)lists.fedoraproject.org
>  To unsubscribe send an email to users-leave(a)lists.fedoraproject.org
>  Fedora Code of Conduct: 
>  https://docs.fedoraproject.org/en-US/project/code-of-conduct/
>  List Guidelines: 
>  https://fedoraproject.org/wiki/Mailing_list_guidelines
>  List Archives: 
>  https://lists.fedoraproject.org/archives/list/[e-mail] 
-- 
Doug H.