12.3 with raid10

could a recompiled kernel somehow disable the proper shutdown process for the array? both my troubled production servers (using custom distribution DVD for install) and my working test server (Not using custom distribution DVD for install) show the same.


vicidialer:~ # cat /proc/version
Linux version 3.7.10-1.28-default (geeko@buildhost) (gcc version 4.7.2 20130108 [gcc-4_7-branch revision 195012] (SUSE Linux) ) #1 SMP Mon Feb 3 14:11:15 UTC 2014 (c9a2c6c)
vicidialer:~ #

How can i tell what options/flags are used when compiling each of these?

Thanks!

well i have done some reading on systemd. I think systemctl is the interface to that. so let me post some stuff and please anyone chime in on this. I am very perplexed on this thing

looks like md.service is running


opensuse12:~ # systemctl list-units -t service --all
UNIT                                  LOAD   ACTIVE   SUB     JOB DESCRIPTION
after.local.service                   loaded active   exited      after.local.service
amavis.service                        error  inactive dead        amavis.service
apparmor.service                      error  inactive dead        apparmor.service
auditd.service                        error  inactive dead        auditd.service
basic.service                         error  inactive dead        basic.service
cifs.service                          loaded inactive dead        LSB: Import remote SMB/ CIFS (MS Windows) file systems
cron.service                          loaded active   running     Command Scheduler
cyrus.service                         error  inactive dead        cyrus.service
dbus.service                          loaded active   running     D-Bus System Message Bus
device-mapper.service                 masked inactive dead        device-mapper.service
dmraid.service                        loaded inactive dead        LSB: start dmraid
earlysyslog.service                   masked inactive dead        earlysyslog.service
emergency.service                     loaded inactive dead        Emergency Shell
exim.service                          error  inactive dead        exim.service
getty@tty1.service                    loaded active   running     Getty on tty1
isdn.service                          error  inactive dead        isdn.service
ldap.service                          error  inactive dead        ldap.service
localfs.service                       loaded inactive dead        Shadow /etc/init.d/boot.localfs
lvm.service                           loaded inactive dead        LSB: Start LVM2
md.service                            loaded active   running     LSB: Multiple Device RAID
mdadmd.service                        loaded active   running     LSB: mdadmd daemon monitoring MD devices
multipath.service                     error  inactive dead        multipath.service
mysql.service                         loaded inactive dead        LSB: Start the MySQL database server
network-remotefs.service              error  inactive dead        network-remotefs.service
network.service                       loaded active   running     LSB: Configure network interfaces and set up routing
NetworkManager.service                error  inactive dead        NetworkManager.service
nfs.service                           loaded inactive dead        LSB: NFS client services
nfsserver.service                     error  inactive dead        nfsserver.service
nmb.service                           error  inactive dead        nmb.service
nscd.service                          loaded active   running     Name Service Cache Daemon
ntp.service                           loaded inactive dead        LSB: Network time protocol daemon (ntpd)
openibd.service                       error  inactive dead        openibd.service
openslp.service                       error  inactive dead        openslp.service
plymouth-quit-wait.service            loaded inactive dead        Wait for Plymouth Boot Screen to Quit
plymouth-quit.service                 loaded inactive dead        Terminate Plymouth Boot Screen
plymouth-read-write.service           loaded inactive dead        Tell Plymouth To Write Out Runtime Data
plymouth-start.service                loaded inactive dead        Show Plymouth Boot Screen
postfix.service                       loaded active   running     Postfix Mail Transport Agent
purge-kernels.service                 loaded inactive dead        Purge old kernels
rc-local.service                      loaded active   exited      /etc/init.d/boot.local Compatibility
rescue.service                        loaded inactive dead        Rescue Shell
rpcbind.service                       loaded inactive dead        RPC Bind
rsyslog.service                       loaded active   running     System Logging Service
scsidev.service                       error  inactive dead        scsidev.service
sendmail.service                      error  inactive dead        sendmail.service
sshd.service                          loaded active   running     OpenSSH Daemon
suse-studio-custom.service            loaded inactive dead        Execute user-provided boot script, if it exists
suse-studio-firstboot.service         error  inactive dead        suse-studio-firstboot.service
SuSEfirewall2.service                 loaded active   exited      SuSEfirewall2 phase 2
SuSEfirewall2_init.service            loaded active   exited      SuSEfirewall2 phase 1
lines 1-51

Also


opensuse12:~ # systemctl status md.service
md.service - LSB: Multiple Device RAID
          Loaded: loaded (/etc/init.d/boot.md)
          Active: active (running) since Mon, 2014-04-21 07:32:17 MST; 9min ago
         Process: 444 ExecStart=/etc/init.d/boot.md start (code=exited, status=0/SUCCESS)
          CGroup: name=systemd:/system/md.service
                  └ 501 @sbin/mdmon md127 --takeover --offroot

Apr 21 07:32:15 opensuse12.doamin.local boot.md[444]: EBUSY - retrying dev_open of /dev/sdb
Apr 21 07:32:15 opensuse12.doamin.local boot.md[444]: EBUSY - retrying dev_open of /dev/sdb
Apr 21 07:32:15 opensuse12.doamin.local boot.md[444]: EBUSY - retrying dev_open of /dev/sdb
Apr 21 07:32:16 opensuse12.doamin.local boot.md[444]: EBUSY - retrying dev_open of /dev/sda
Apr 21 07:32:16 opensuse12.doamin.local boot.md[444]: EBUSY - retrying dev_open of /dev/sda
Apr 21 07:32:16 opensuse12.doamin.local boot.md[444]: EBUSY - retrying dev_open of /dev/sda
Apr 21 07:32:16 opensuse12.doamin.local boot.md[444]: EBUSY - retrying dev_open of /dev/sda
Apr 21 07:32:17 opensuse12.doamin.local boot.md[444]: EBUSY - retrying dev_open of /dev/sda
Apr 21 07:32:17 opensuse12.doamin.local boot.md[444]: ..done
Apr 21 07:32:17 opensuse12.doamin.local systemd[1]: Started LSB: Multiple Device RAID.
opensuse12:~ #

chkconfig shows mdadmd is on


opensuse12:~ # chkconfig mdadmd
mdadmd  on
opensuse12:~ #

ps aux shows


opensuse12:~ # ps aux | grep md
root        25  0.0  0.0      0     0 ?        S<   07:32   0:00 [md]
root        29  0.0  0.0      0     0 ?        SN   07:32   0:00 [ksmd]
root       229  7.2  0.0      0     0 ?        S    07:32   0:33 [md126_raid10]
root       233  0.0  0.2  14932 10836 ?        SLsl 07:32   0:00 @dmon --offroot md127
root       238  1.7  0.0      0     0 ?        D    07:32   0:08 [md126_resync]
root       341  0.0  0.0      0     0 ?        S    07:32   0:00 [jbd2/md126p2-8]
root       374  0.0  0.2 120500 11120 ?        Ss   07:32   0:00 /usr/lib/systemd/systemd-journald
root       398  0.0  0.0  38580  1828 ?        Ss   07:32   0:00 /usr/lib/systemd/systemd-udevd
root       501  0.0  0.2  15004 10908 ?        SLsl 07:32   0:00 @sbin/mdmon md127 --takeover --offroot
root       597  0.0  0.0   4876   844 ?        Ss   07:32   0:00 /sbin/mdadm -F -d 60 -m root@localhost -s -c /etc/mdadm.conf
root       625  0.0  0.0  26380  1540 ?        Ss   07:32   0:00 /usr/lib/systemd/systemd-logind
message+   662  0.0  0.0  30048  1616 ?        Ss   07:32   0:00 /bin/dbus-daemon --system --address=systemd: --nofork --nopidfile --systemd-activation
root      2691  0.0  0.0   7052   864 pts/1    S+   07:39   0:00 grep --color=auto md
opensuse12:~ #

This does not look right. The second one was expected to kill the first one. I do not say it is necessary problem, but mdmon is the one responsible for marking array clean and I do not know how multiple mdmon’s watching the same device behave.

I briefly tested installation of 13.1 on fake DDF array and I have only one process running, @sbin/mdmon; @mdmon is not present.

Hmm … the very first question - are you using standard mkinitrd or dracut on a system that has problems?

sorry for my delay in getting back on this. I am not sure how to tell. Since i have nothing on my file system with the letters “dracut” in them and i have approx 150 files with “mkinirtd” lletters in them, I am going with mkinitrd. This is to make the initial ram disk, is it not?