On Mon, Sep 18, 2017 at 6:18 PM, Sven Hartge <s...@svenhartge.de> wrote:
> Roman Serbski <r.serbski.gro...@gmail.com> wrote:
>
>> /etc/fstab
>
>> ###
>> /dev/drbd0           /var/www         ocfs2   noauto,noatime       0       0
>> ###
>
>> After the reboot, no /var/www is mounted.
>
> Missing "_netdev"?

Thank you. Tried that -- no difference.

>> The status of both o2cb and ocfs2 services is inactive (dead) with the
>> ocfs2 cluster offline:
>
>> $ service o2cb status
>> o2cb.service - LSB: Load O2CB cluster services at system boot.
>>    Loaded: loaded (/etc/init.d/o2cb; generated; vendor preset: enabled)
>>    Active: inactive (dead)
>>      Docs: man:systemd-sysv-generator(8)
>
>> $ service ocfs2 status
>> ocfs2.service - LSB: Mount OCFS2 volumes at boot.
>>    Loaded: loaded (/etc/init.d/ocfs2; generated; vendor preset: enabled)
>>    Active: inactive (dead)
>>      Docs: man:systemd-sysv-generator(8)
>
> Maybe o2cb and ocfs2 need to be ordered after network-online.target?

I thought about it too, but according to /etc/init.d/o2cb and
/etc/init.d/ocfs2 they seem to start after $network:

#!/bin/bash
# init fragment for O2CB.
#
# chkconfig: 2345 24 19
# description: Load O2CB cluster services at system boot.
#
### BEGIN INIT INFO
# Provides: o2cb
# Required-Start: $network $local_fs
# Required-Stop: $network $local_fs
# Default-Start: 2 3 4 5
# Default-Stop: 0 1 6
# Short-Description: Load O2CB cluster services at system boot.
# Description: Load O2CB cluster services at system boot.
### END INIT INFO

#! /bin/bash
# Copyright (c) 2005 Oracle
# All rights reserved.
#
# chkconfig: 2345 25 18
# description: Mount OCFS2 volumes at boot.
#
### BEGIN INIT INFO
# Provides: ocfs2
# Required-Start: $local_fs $network o2cb
# Required-Stop: $local_fs $network o2cb
# Should-Start: drbd iscsi multipath-tools
# Should-Stop: drbd iscsi multipath-tools
# Default-Start: 2 3 4 5
# Default-Stop: 0 1 6
# Short-Description: Mount OCFS2 volumes at boot.
# Description:  Mount OCFS2 volumes at boot.
### END INIT INFO

> Any output after a failed boot from "journalctl -b -u  o2cb.service" or
> "journalctl -b -u ocfs2.service"?

Nothing there:

$ journalctl -b -u o2cb.service
-- Logs begin at Tue 2017-09-19 10:13:16 CEST, end at Tue 2017-09-19
11:17:01 CEST. --
-- No entries --

$ journalctl -b -u ocfs2.service
-- Logs begin at Tue 2017-09-19 10:13:16 CEST, end at Tue 2017-09-19
11:17:01 CEST. --
-- No entries --

Thanks.

Reply via email to