drbd data: failed to create debugfs dentry
CentOS 7 kernel release 3.10.0-957.el7.x86_64
drbd 9.0.16-1
Have one resource configured. drbd servicve is not enabled to start at boot time. I reboot the two nodes. One the first node I run systemctl start drbd and get
"DRBD's startup script waits for the peer node(s) to appear.
On second now when I run systemctl start drbd I get:
drbd data: failed to create debugfs dentry
EDIT
When I run drbdadm up resource_name on both nodes with drbd service disable and not started I get the two nodes in Secondary/UpToDate state which is good.
EDIT2
global_common.conf
data.res
All resource are started on otrs1. It has the Primary role bot shows connecting for the remote node, and on the remote node I don't see the other node at all.
When I run pcs cluster stop --all and next run drbdadm up data on both nodes all looks good.
Now when I mount /dev/drbd1 /opt/otrs on one of the nodes it gets auto promoted to the primary role.
Now when I umount and bring the reource down on both nodes and re-run drbdadm status I get obviously No currently configured DRBD found.
Now, exactly the same happens when I run systemctl start drbd on both. On first node the output appears to hand but I guess it waits for the other node to start its services as well, right ?
After a reboot, the cluster and resources start on node 1 but after putting it into standby mode, resources are not moved:
And here's what I see journalctl -xe
EDIT3
ok that's odd
I was loading the drbd kernel module at boot via /etc/modules-load.d/drbd.conf on both nodes but disabled it. Rebooted and to my suprise on one node it's loaded but without drbd_transport_tcp, is pacemaker loading the drbd kernel_module? I can't imagine that.
Now when I systemctl disable pcsd; systemctl disable pacemaker; systemctl disable corosync on both node and reboot an do lsmod | grep drbd it returns no results. I don't get it :(
drbd
asked Feb 14 at 8:54
blablatraceblablatrace
738
add a comment |
CentOS 7 kernel release 3.10.0-957.el7.x86_64
drbd 9.0.16-1
Have one resource configured. drbd servicve is not enabled to start at boot time. I reboot the two nodes. One the first node I run systemctl start drbd and get
"DRBD's startup script waits for the peer node(s) to appear.
On second now when I run systemctl start drbd I get:
drbd data: failed to create debugfs dentry
EDIT
When I run drbdadm up resource_name on both nodes with drbd service disable and not started I get the two nodes in Secondary/UpToDate state which is good.
EDIT2
global_common.conf
data.res
All resource are started on otrs1. It has the Primary role bot shows connecting for the remote node, and on the remote node I don't see the other node at all.
When I run pcs cluster stop --all and next run drbdadm up data on both nodes all looks good.
Now when I mount /dev/drbd1 /opt/otrs on one of the nodes it gets auto promoted to the primary role.
Now when I umount and bring the reource down on both nodes and re-run drbdadm status I get obviously No currently configured DRBD found.
Now, exactly the same happens when I run systemctl start drbd on both. On first node the output appears to hand but I guess it waits for the other node to start its services as well, right ?
After a reboot, the cluster and resources start on node 1 but after putting it into standby mode, resources are not moved:
And here's what I see journalctl -xe
EDIT3
ok that's odd
I was loading the drbd kernel module at boot via /etc/modules-load.d/drbd.conf on both nodes but disabled it. Rebooted and to my suprise on one node it's loaded but without drbd_transport_tcp, is pacemaker loading the drbd kernel_module? I can't imagine that.
Now when I systemctl disable pcsd; systemctl disable pacemaker; systemctl disable corosync on both node and reboot an do lsmod | grep drbd it returns no results. I don't get it :(
drbd
asked Feb 14 at 8:54
blablatraceblablatrace
738
1
Can you share your DRBD configuration with us? Also, what version ofkmod-drbdto you have installed?
– Matt Kereczman
Feb 15 at 17:26
@MattKereczman Thank you for looking into my issue! Please see the EDIT section of my post. Thank you! PS.kmod-drbdversion is on bothkmod-drbd90-9.0.16-1.el7_6.elrepo.x86_64
– blablatrace
Feb 16 at 16:55
add a comment |
CentOS 7 kernel release 3.10.0-957.el7.x86_64
drbd 9.0.16-1
Have one resource configured. drbd servicve is not enabled to start at boot time. I reboot the two nodes. One the first node I run systemctl start drbd and get
"DRBD's startup script waits for the peer node(s) to appear.
On second now when I run systemctl start drbd I get:
drbd data: failed to create debugfs dentry
EDIT
When I run drbdadm up resource_name on both nodes with drbd service disable and not started I get the two nodes in Secondary/UpToDate state which is good.
EDIT2
global_common.conf
data.res
All resource are started on otrs1. It has the Primary role bot shows connecting for the remote node, and on the remote node I don't see the other node at all.
When I run pcs cluster stop --all and next run drbdadm up data on both nodes all looks good.
Now when I mount /dev/drbd1 /opt/otrs on one of the nodes it gets auto promoted to the primary role.
Now when I umount and bring the reource down on both nodes and re-run drbdadm status I get obviously No currently configured DRBD found.
Now, exactly the same happens when I run systemctl start drbd on both. On first node the output appears to hand but I guess it waits for the other node to start its services as well, right ?
After a reboot, the cluster and resources start on node 1 but after putting it into standby mode, resources are not moved:
And here's what I see journalctl -xe
EDIT3
ok that's odd
I was loading the drbd kernel module at boot via /etc/modules-load.d/drbd.conf on both nodes but disabled it. Rebooted and to my suprise on one node it's loaded but without drbd_transport_tcp, is pacemaker loading the drbd kernel_module? I can't imagine that.
Now when I systemctl disable pcsd; systemctl disable pacemaker; systemctl disable corosync on both node and reboot an do lsmod | grep drbd it returns no results. I don't get it :(
drbd
asked Feb 14 at 8:54
blablatraceblablatrace
738
CentOS 7 kernel release 3.10.0-957.el7.x86_64
drbd 9.0.16-1
Have one resource configured. drbd servicve is not enabled to start at boot time. I reboot the two nodes. One the first node I run systemctl start drbd and get
"DRBD's startup script waits for the peer node(s) to appear.
On second now when I run systemctl start drbd I get:
drbd data: failed to create debugfs dentry
EDIT
When I run drbdadm up resource_name on both nodes with drbd service disable and not started I get the two nodes in Secondary/UpToDate state which is good.
EDIT2
global_common.conf
data.res
All resource are started on otrs1. It has the Primary role bot shows connecting for the remote node, and on the remote node I don't see the other node at all.
When I run pcs cluster stop --all and next run drbdadm up data on both nodes all looks good.
Now when I mount /dev/drbd1 /opt/otrs on one of the nodes it gets auto promoted to the primary role.
Now when I umount and bring the reource down on both nodes and re-run drbdadm status I get obviously No currently configured DRBD found.
Now, exactly the same happens when I run systemctl start drbd on both. On first node the output appears to hand but I guess it waits for the other node to start its services as well, right ?
After a reboot, the cluster and resources start on node 1 but after putting it into standby mode, resources are not moved:
And here's what I see journalctl -xe
EDIT3
ok that's odd
I was loading the drbd kernel module at boot via /etc/modules-load.d/drbd.conf on both nodes but disabled it. Rebooted and to my suprise on one node it's loaded but without drbd_transport_tcp, is pacemaker loading the drbd kernel_module? I can't imagine that.
Now when I systemctl disable pcsd; systemctl disable pacemaker; systemctl disable corosync on both node and reboot an do lsmod | grep drbd it returns no results. I don't get it :(
drbd
drbd
asked Feb 14 at 8:54
blablatraceblablatrace
738
asked Feb 14 at 8:54
blablatraceblablatrace
738
edited Feb 16 at 21:01
blablatrace
asked Feb 14 at 8:54
blablatraceblablatrace
738
asked Feb 14 at 8:54
blablatraceblablatrace
738
asked Feb 14 at 8:54
blablatraceblablatrace
738
738
1
Can you share your DRBD configuration with us? Also, what version ofkmod-drbdto you have installed?
– Matt Kereczman
Feb 15 at 17:26
@MattKereczman Thank you for looking into my issue! Please see the EDIT section of my post. Thank you! PS.kmod-drbdversion is on bothkmod-drbd90-9.0.16-1.el7_6.elrepo.x86_64
– blablatrace
Feb 16 at 16:55
add a comment |
1
Can you share your DRBD configuration with us? Also, what version ofkmod-drbdto you have installed?
– Matt Kereczman
Feb 15 at 17:26
@MattKereczman Thank you for looking into my issue! Please see the EDIT section of my post. Thank you! PS.kmod-drbdversion is on bothkmod-drbd90-9.0.16-1.el7_6.elrepo.x86_64
– blablatrace
Feb 16 at 16:55
1
1
Can you share your DRBD configuration with us? Also, what version of
kmod-drbd to you have installed?– Matt Kereczman
Feb 15 at 17:26
Can you share your DRBD configuration with us? Also, what version of
kmod-drbd to you have installed?– Matt Kereczman
Feb 15 at 17:26
@MattKereczman Thank you for looking into my issue! Please see the EDIT section of my post. Thank you! PS.
kmod-drbd version is on both kmod-drbd90-9.0.16-1.el7_6.elrepo.x86_64– blablatrace
Feb 16 at 16:55
@MattKereczman Thank you for looking into my issue! Please see the EDIT section of my post. Thank you! PS.
kmod-drbd version is on both kmod-drbd90-9.0.16-1.el7_6.elrepo.x86_64– blablatrace
Feb 16 at 16:55
add a comment |
1 Answer
1
active
oldest
votes
If you're using Pacemaker, which you are, then you should disable DRBD in systemd, allowing Pacemaker to have full control of starting/stopping DRBD.
# systemctl disable drbd
DRBD should load it's transport modules when it brings up it's connections, and drbdadm up <res> should load the DRBD kernel module if it isn't already loaded.
answered Feb 19 at 17:32
Matt KereczmanMatt Kereczman
56227
Thank you Matt but drbd service was not running and disable on both nodes from starting during boot. What I did, I've addedauto-promote noin theglobal_common.confon both nodes. I also discovered that there was a spli brain condition reportedjournalctl | grep split. What I did next, stopped the corosync service on both nodes and followed docs.linbit.com/docs/users-guide-9.0/#s-resolve-split-brain . Was it the correct way to resolve a split brain condition ?
– blablatrace
Feb 19 at 19:38
1
That is the correct way to resolve a split brain. Do you happen to have anything being "denied" in/var/log/audit/audit.log?
– Matt Kereczman
Feb 19 at 23:31
Yes, but I think this was related toselinuxbeing enabled on node2.
– blablatrace
Feb 20 at 9:38
add a comment |
Your Answer
StackExchange.ready(function() {
var channelOptions = {
tags: "".split(" "),
id: "106"
};
initTagRenderer("".split(" "), "".split(" "), channelOptions);
StackExchange.using("externalEditor", function() {
// Have to fire editor after snippets, if snippets enabled
if (StackExchange.settings.snippets.snippetsEnabled) {
StackExchange.using("snippets", function() {
createEditor();
});
}
else {
createEditor();
}
});
function createEditor() {
StackExchange.prepareEditor({
heartbeatType: 'answer',
autoActivateHeartbeat: false,
convertImagesToLinks: false,
noModals: true,
showLowRepImageUploadWarning: true,
reputationToPostImages: null,
bindNavPrevention: true,
postfix: "",
imageUploader: {
brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
allowUrls: true
},
onDemand: true,
discardSelector: ".discard-answer"
,immediatelyShowMarkdownHelp:true
});
}
});
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2funix.stackexchange.com%2fquestions%2f500566%2fdrbd-data-failed-to-create-debugfs-dentry%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
1 Answer
1
active
oldest
votes
1 Answer
1
active
oldest
votes
active
oldest
votes
active
oldest
votes
If you're using Pacemaker, which you are, then you should disable DRBD in systemd, allowing Pacemaker to have full control of starting/stopping DRBD.
# systemctl disable drbd
DRBD should load it's transport modules when it brings up it's connections, and drbdadm up <res> should load the DRBD kernel module if it isn't already loaded.
answered Feb 19 at 17:32
Matt KereczmanMatt Kereczman
56227
Thank you Matt but drbd service was not running and disable on both nodes from starting during boot. What I did, I've addedauto-promote noin theglobal_common.confon both nodes. I also discovered that there was a spli brain condition reportedjournalctl | grep split. What I did next, stopped the corosync service on both nodes and followed docs.linbit.com/docs/users-guide-9.0/#s-resolve-split-brain . Was it the correct way to resolve a split brain condition ?
– blablatrace
Feb 19 at 19:38
1
That is the correct way to resolve a split brain. Do you happen to have anything being "denied" in/var/log/audit/audit.log?
– Matt Kereczman
Feb 19 at 23:31
Yes, but I think this was related toselinuxbeing enabled on node2.
– blablatrace
Feb 20 at 9:38
add a comment |
If you're using Pacemaker, which you are, then you should disable DRBD in systemd, allowing Pacemaker to have full control of starting/stopping DRBD.
# systemctl disable drbd
DRBD should load it's transport modules when it brings up it's connections, and drbdadm up <res> should load the DRBD kernel module if it isn't already loaded.
answered Feb 19 at 17:32
Matt KereczmanMatt Kereczman
56227
Thank you Matt but drbd service was not running and disable on both nodes from starting during boot. What I did, I've addedauto-promote noin theglobal_common.confon both nodes. I also discovered that there was a spli brain condition reportedjournalctl | grep split. What I did next, stopped the corosync service on both nodes and followed docs.linbit.com/docs/users-guide-9.0/#s-resolve-split-brain . Was it the correct way to resolve a split brain condition ?
– blablatrace
Feb 19 at 19:38
1
That is the correct way to resolve a split brain. Do you happen to have anything being "denied" in/var/log/audit/audit.log?
– Matt Kereczman
Feb 19 at 23:31
Yes, but I think this was related toselinuxbeing enabled on node2.
– blablatrace
Feb 20 at 9:38
add a comment |
If you're using Pacemaker, which you are, then you should disable DRBD in systemd, allowing Pacemaker to have full control of starting/stopping DRBD.
# systemctl disable drbd
DRBD should load it's transport modules when it brings up it's connections, and drbdadm up <res> should load the DRBD kernel module if it isn't already loaded.
answered Feb 19 at 17:32
Matt KereczmanMatt Kereczman
56227
If you're using Pacemaker, which you are, then you should disable DRBD in systemd, allowing Pacemaker to have full control of starting/stopping DRBD.
# systemctl disable drbd
DRBD should load it's transport modules when it brings up it's connections, and drbdadm up <res> should load the DRBD kernel module if it isn't already loaded.
answered Feb 19 at 17:32
Matt KereczmanMatt Kereczman
56227
answered Feb 19 at 17:32
Matt KereczmanMatt Kereczman
56227
answered Feb 19 at 17:32
Matt KereczmanMatt Kereczman
56227
answered Feb 19 at 17:32
Matt KereczmanMatt Kereczman
56227
56227
Thank you Matt but drbd service was not running and disable on both nodes from starting during boot. What I did, I've addedauto-promote noin theglobal_common.confon both nodes. I also discovered that there was a spli brain condition reportedjournalctl | grep split. What I did next, stopped the corosync service on both nodes and followed docs.linbit.com/docs/users-guide-9.0/#s-resolve-split-brain . Was it the correct way to resolve a split brain condition ?
– blablatrace
Feb 19 at 19:38
1
That is the correct way to resolve a split brain. Do you happen to have anything being "denied" in/var/log/audit/audit.log?
– Matt Kereczman
Feb 19 at 23:31
Yes, but I think this was related toselinuxbeing enabled on node2.
– blablatrace
Feb 20 at 9:38
add a comment |
Thank you Matt but drbd service was not running and disable on both nodes from starting during boot. What I did, I've addedauto-promote noin theglobal_common.confon both nodes. I also discovered that there was a spli brain condition reportedjournalctl | grep split. What I did next, stopped the corosync service on both nodes and followed docs.linbit.com/docs/users-guide-9.0/#s-resolve-split-brain . Was it the correct way to resolve a split brain condition ?
– blablatrace
Feb 19 at 19:38
1
That is the correct way to resolve a split brain. Do you happen to have anything being "denied" in/var/log/audit/audit.log?
– Matt Kereczman
Feb 19 at 23:31
Yes, but I think this was related toselinuxbeing enabled on node2.
– blablatrace
Feb 20 at 9:38
Thank you Matt but drbd service was not running and disable on both nodes from starting during boot. What I did, I've added
auto-promote no in the global_common.conf on both nodes. I also discovered that there was a spli brain condition reported journalctl | grep split. What I did next, stopped the corosync service on both nodes and followed docs.linbit.com/docs/users-guide-9.0/#s-resolve-split-brain . Was it the correct way to resolve a split brain condition ?– blablatrace
Feb 19 at 19:38
Thank you Matt but drbd service was not running and disable on both nodes from starting during boot. What I did, I've added
auto-promote no in the global_common.conf on both nodes. I also discovered that there was a spli brain condition reported journalctl | grep split. What I did next, stopped the corosync service on both nodes and followed docs.linbit.com/docs/users-guide-9.0/#s-resolve-split-brain . Was it the correct way to resolve a split brain condition ?– blablatrace
Feb 19 at 19:38
1
1
That is the correct way to resolve a split brain. Do you happen to have anything being "denied" in
/var/log/audit/audit.log?– Matt Kereczman
Feb 19 at 23:31
That is the correct way to resolve a split brain. Do you happen to have anything being "denied" in
/var/log/audit/audit.log?– Matt Kereczman
Feb 19 at 23:31
Yes, but I think this was related to
selinux being enabled on node2.– blablatrace
Feb 20 at 9:38
Yes, but I think this was related to
selinux being enabled on node2.– blablatrace
Feb 20 at 9:38
add a comment |
Thanks for contributing an answer to Unix & Linux Stack Exchange!
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2funix.stackexchange.com%2fquestions%2f500566%2fdrbd-data-failed-to-create-debugfs-dentry%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
1
Can you share your DRBD configuration with us? Also, what version of
kmod-drbdto you have installed?– Matt Kereczman
Feb 15 at 17:26
@MattKereczman Thank you for looking into my issue! Please see the EDIT section of my post. Thank you! PS.
kmod-drbdversion is on bothkmod-drbd90-9.0.16-1.el7_6.elrepo.x86_64– blablatrace
Feb 16 at 16:55