[Expired for linux (Ubuntu) because there has been no activity for 60
days.]
** Changed in: linux (Ubuntu)
Status: Incomplete => Expired
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1614038
T
I also can confirm that this is:
3.13.0-123-generic: /sys/kernel/config/cluster/ocfs2/heartbeat/dead_threshold
4.4.0-81-generic: /sys/kernel/config/cluster/ocfs2/heartbeat/threshold
So where does the change come from and what needs to adapt (kernel or ocfs
tools).
It was reported that upstream in
Hi,
I have to beg all your pardon - nothing has happened since the last updates.
I'm trying to clear a few bugs that seem to expire by being dormant.
On this one the first that I can provide is a trivial reproduction which often
helps to get more general developers to focus on an issue and not fee
Any updates on this issue? It is blocking our move to 16.04. Hunting
for work arounds now, other than just accepting the default.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1614038
Title:
o2cb
Note that looking at kernel git, dead_threshold still seem to be the
right value.
I don't known why on last ubuntu/debian kernel it's now "threshold".
I'll try to build a stock kernel to compare.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed
Thanks Alexandre for your additional logs and potential fix. This will
get looked at for the next release to understand if that is the right
fix going forward.
** Tags added: server-next
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
set_timeouts()
{
O2CB_HEARTBEAT_THRESHOLD_FILE_OLD=/proc/fs/ocfs2_nodemanager/hb_dead_threshold
-
O2CB_HEARTBEAT_THRESHOLD_FILE=$(configfs_path)/cluster/${CLUSTER}/heartbeat/dead_threshold
+
O2CB_HEARTBEAT_THRESHOLD_FILE=$(configfs_path)/cluster/${CLUSTER}/heartbeat/threshold
--
You
Hi,
I have same problem than you with debian jessie and kernel 4.7.
works fine with kernel 3.16
I seem that on kernel 3.16,
the sysfs threshold was
/sys/kernel/config/cluster/ocfs2/heartbeat/dead_threshold
and now on 4.7
/sys/kernel/config/cluster/ocfs2/heartbeat/threshold
the o2cb init scrip
** Changed in: ocfs2-tools (Ubuntu)
Status: Incomplete => Triaged
** Changed in: ocfs2-tools (Ubuntu)
Importance: Undecided => Medium
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1614038
T
** Attachment added: "default-o2bc"
https://bugs.launchpad.net/ubuntu/+source/ocfs2-tools/+bug/1614038/+attachment/4731556/+files/default-o2bc
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1614038
Yes, sorry ... I should have added the config files... I'll do that now.
These files are identical across all 4 nodes.
There are additional references in the file for "sentinel", "belt" and
"moli7". These are not part of the main cluster file system, but are
used for other ocfs2 volumes.
** At
Thank you for taking the time to report this bug and helping to make
Ubuntu better.
Since there isn't enough information in your report to differentiate
between a local configuration problem and a bug in Ubuntu, I'm marking
this bug as Incomplete.
If indeed this is a local configuration problem,
12 matches
Mail list logo
