Launchpad has imported 23 comments from the remote bug at
https://bugzilla.redhat.com/show_bug.cgi?id=338511.
If you reply to an imported comment from within Launchpad, your comment
will be sent to the remote bug automatically. Read more about
Launchpad's inter-bugtracker facilities at
https://hel
** Changed in: redhat-cluster-suite (Ubuntu)
Status: Fix Committed => Fix Released
--
Node hangs at clvm when joining cluster
https://bugs.launchpad.net/bugs/158288
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact for Ubuntu.
--
ubuntu-
And I can report that kernel that just landed into Gutsy solved this
issue.
Big thanks to everyone involved.
--
Node hangs at clvm when joining cluster
https://bugs.launchpad.net/bugs/158288
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact for
Thanks! These have been committed for the next kernel update.
** Changed in: redhat-cluster-suite (Ubuntu)
Status: Confirmed => Fix Committed
--
Node hangs at clvm when joining cluster
https://bugs.launchpad.net/bugs/158288
You received this bug notification because you are a member of U
Stephen, awesome. I will try to fix that warning too. It should be
trivial.
Thanks
Fabio
--
Node hangs at clvm when joining cluster
https://bugs.launchpad.net/bugs/158288
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact for Ubuntu.
--
ubuntu-
Hi Kees,
this patch contains the gutsy fixes and a detailed explanation on how it was
built
(git sha1 cherry picks and so on).
Fabio
** Attachment added: "gutsy fix"
http://launchpadlibrarian.net/10679492/gutsy.diff
--
Node hangs at clvm when joining cluster
https://bugs.launchpad.net/bugs
Hi Kees,
same patch as above for feisty. Same logic but note that it is slightly
different
and can't be cherry picked.
In detail there are a couple of extra changes required to make the gutsy
patch work:
static void make_sockaddr: didn't memset the sock_addr structure leaving dirty
info around
Hi Kees,
this is the dapper patch based on the others. It's still impossible to
cherry pick without solving lots of conflicts.
You want to notice these small differences compared to the other
patches:
static void make_sockaddr: it didn't use sock_storage but sockadd_in6
casted around. We memset
Hi Kees,
the situation in edgy is way simpler. We disabled gfs2 that is the only
in kernel client for fs/dlm.
The patch simply disable fs/dlm as it is not required. It is _not_ worth
spending time fixing it at all.
Fabio
** Attachment added: "edgy fix"
http://launchpadlibrarian.net/10679638/
Brilliant - it works!
I have tested with a cold boot of all 3 machines and with one-by-one
reboots and everything works fine. I do get one odd message when I
shut down any of the nodes:
[ 701.550624] slab error in kmem_cache_destroy(): cache 'dlm_conn':
Can't free all objects
But asides from t
Stephen,
make sure to keep a copy of the old kernel around.. I can't test it myself as I
lack amd64 and i don't want you
to end up with unbootable machines around.
Thanks a lot
Fabio
PS weekend is good.
--
Node hangs at clvm when joining cluster
https://bugs.launchpad.net/bugs/158288
You rece
Fabio,
Thanks ever so much. I will have to wait until the weekend to test,
as this is a 'live' cluster. Will report back ASAP.
Cheers,
Stephen
On 11/29/07, Fabio Massimo Di Nitto <[EMAIL PROTECTED]> wrote:
> Stephen: I have a test kernel for you..
>
> http://people.ubuntu.com/~fabbione/dlm/li
Stephen: I have a test kernel for you..
http://people.ubuntu.com/~fabbione/dlm/linux-
image-2.6.15-29-amd64-server_2.6.15-29.60_amd64.deb
Please install it on the entire cluster. You will need to reboot all of it in
one go unfortunately and please test
like Ante did, by booting the whole cluster
funkypantsboy: I haven't ported the patch back to dapper yet.
A kernel update will come shortly after. probably a matter of few days.
FAbio
--
Node hangs at clvm when joining cluster
https://bugs.launchpad.net/bugs/158288
You received this bug notification because you are a member of Ubuntu
Bug
I don't have a deb. I applied this patch to gutsy kernel source and
build it.
--
Node hangs at clvm when joining cluster
https://bugs.launchpad.net/bugs/158288
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact for Ubuntu.
--
ubuntu-bugs mailing
Awesome - thanks.
Any chance I could get a patched .deb to test with on our 3-node
cluster?
Stephen
--
Node hangs at clvm when joining cluster
https://bugs.launchpad.net/bugs/158288
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact for Ubuntu.
This patch solves the problem. Testing done:
node1 - 2 quorum points
node2 - 1 quorum points
quorum - 2 points
simultaneous reboot - OK
node2 reboot while node1 running - OK
node1 reboot while node2 running - OK
--
Node hangs at clvm when joining cluster
https://bugs.launchpad.net/bugs/158288
Y
Will test it tomorrow. Thanks.
--
Node hangs at clvm when joining cluster
https://bugs.launchpad.net/bugs/158288
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact for Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://list
Ante: can you please test this other patch instead? it is on top of
2.6.22 gutsy kernel sources.
If this one work, i will take care to propagate the fixes down to
dapper.
remember you will need to reboot the entire cluster and hint: add that famous
printk to make sure
you are running a patched k
** Changed in: redhat-cluster-suite (Fedora)
Status: Fix Committed => Fix Released
--
Node hangs at clvm when joining cluster
https://bugs.launchpad.net/bugs/158288
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact for Ubuntu.
--
ubuntu-
We need to work this out with upstream because it appears that the fix
they committed doesn't work for Ante.
Fabio
--
Node hangs at clvm when joining cluster
https://bugs.launchpad.net/bugs/158288
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contac
http://people.ubuntu.com/~fabbione/foo.diff - this didn't do the trick
for me. Same results.
I'm wondering, is 'make_sockaddr(&saddr, dlm_config.ci_tcp_port,
&addr_len);' still needed since make_sockaddr is already executed? This
way we again get more than one connection at the same time.
--
Nod
** Changed in: redhat-cluster-suite (Fedora)
Status: Unknown => Fix Committed
--
Node hangs at clvm when joining cluster
https://bugs.launchpad.net/bugs/158288
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact for Ubuntu.
--
ubuntu-bugs
Awesome - thanks.
I can test a potential fixes if that would help.
Stephen
--
Node hangs at clvm when joining cluster
https://bugs.launchpad.net/bugs/158288
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact for Ubuntu.
--
ubuntu-bugs mailing
Stephen,
we are working to get this addressed asap. A fix is already available from
upstream and we are testing it to make sure
it addresses the problem 100%.
Fabio
** Changed in: redhat-cluster-suite (Ubuntu)
Importance: Medium => Critical
Assignee: (unassigned) => Fabio Massimo Di Nit
I can confirm this. And will test a patch for it.
** Changed in: redhat-cluster-suite (Ubuntu)
Importance: Undecided => Medium
Status: New => Confirmed
--
Node hangs at clvm when joining cluster
https://bugs.launchpad.net/bugs/158288
You received this bug notification because you are a
I cross-posted this bug to the Linux Clustering mailing list. I
received a response from one of the list members that "That sounds like
a bug that has already been fixed. I don't have the reference to hand
...". So this looks like a known problem that has been fixed upstream.
Stephen
--
Node
27 matches
Mail list logo
