Welcome to the Linux Foundation Forum!

What's the equivalent service for dmmonitor in CentOS 7?

I found dmmonitor doesn't exists in Centos7, I assume mdmon is the equivalent but I 'm not sure...
Thanks

Welcome!

It looks like you're new here. Sign in or register to get started.
Sign In

Comments

  • Hi @nicolasmendoza ,

    Are you talking about Multipathing? Because I couldn't find any "dmmonitor" tool. Is that the right command name?
    In case you refers to Multipathing, you can search for "device-mapper-multipath.x86_64" on CentOS 7.

    Regards,
    Luis.

  • Posts: 916

    we don't know what you are talking about. Googling on dmmonitor takes me to Windows documentation on data bases. There is no such tool in LInux AFAIK.

  • Posts: 22
    edited September 2020

    I think "mdmonitor" is the name of service...
    Sorry for the typo.

  • Posts: 916

    sudo systemctl [start/stop/restart/enable/disable] mdmonitor.service

    It is now a systemd service in RHEL 8 and RHEL 7. RHEL 8 does not seem to have /etc/mdadm.conf.

    To be honest I haven't used software raid for ages (the hardware raid is better as is mentioned in the course and have thought about eliminating this section.) We will have to go back and see what if anything needs modifcation in the course to make the lab work etc.

    Next time please correct your typo faster as several of us went down the rabbit hole. Telling us exactly what section it referred to would have helped.

  • Thanks, I appreciate to learn about your experience with RAID.
    Yes, i will try to review better my questions before post.

  • Posts: 99

    A little note on Chapter 24 / RAID and Ubuntu:

    You mention that "on Ubuntu systems, the service is called mdadm rather than mdmonitor."

    Here is what I get on a Ubuntu 18.04 system:

    1. $ sudo systemctl start mdadm
    2. Failed to start mdadm.service: Unit mdadm.service is masked.
    3. $ sudo systemctl status mdadm
    4. mdadm.service
    5. Loaded: masked (/dev/null; bad)
    6. Active: inactive (dead)
    7.  

    However, mdmonitor works like a champ:

    1. $ sudo systemctl start mdmonitor.service
    2. $ sudo systemctl status mdmonitor.service
    3. mdmonitor.service - MD array monitor
    4. Loaded: loaded (/lib/systemd/system/mdmonitor.service; static; vendor preset:
    5. Active: active (running) since Tue 2020-10-06 12:34:25 IDT; 7s ago
    6. Main PID: 3518 (mdadm)
    7. Tasks: 1 (limit: 4915)
    8. CGroup: /system.slice/mdmonitor.service
    9. └─3518 /sbin/mdadm --monitor --scan
    10.  
    11. Oct 06 12:34:25 worker4 systemd[1]: Started MD array monitor.
    12.  

    It seems to execute mdadm --monitor --scan, though.

    About deleting the chapter, the less we need to study, the better ;) . But unfortunately in real life we could learn a tough lesson when implementing hardware RAID and not purchasing enough spare controllers. mdadm always works. That's the beauty of Linux.

  • Hi @heiko_s ,

    About deleting the chapter, the less we need to study, the better ;) . But unfortunately in real life we could learn a tough lesson when implementing hardware RAID and not purchasing enough spare controllers. mdadm always works. That's the beauty of Linux.

    Yes, it might be beautiful, hehehe. But it's not all honey and flakes, as the maintenance and repair of a software RAID could get large more complex than hardware RAID.

    Many regard,
    Luis.

Welcome!

It looks like you're new here. Sign in or register to get started.
Sign In

Welcome!

It looks like you're new here. Sign in or register to get started.
Sign In

Categories

Upcoming Training