On Sun, Aug 19, 2007 at 07:32:57AM +0200, Fabio Massimo Di Nitto wrote:
David Teigland wrote:
I believe that the correct solution is to install the necessary kernel
headers into /usr/include/linux/ prior to building cluster. This
usually means doing something like this:
cd /usr
On Fri, Aug 24, 2007 at 02:06:29PM +0200, Fabio Massimo Di Nitto wrote:
Hi David,
any objections to this cleanup?
It's very simple and just put inline the makefile with all the others.
note that we don't build tests by default or ship them. This is not changed.
Looks good, thanks.
On Mon, Aug 27, 2007 at 05:00:06PM +0100, Steven Whitehouse wrote:
From 2a666f519dd12e8b3a82d1e16cad3114cfdd917d Mon Sep 17 00:00:00 2001
From: Steven Whitehouse [EMAIL PROTECTED]
Date: Mon, 27 Aug 2007 16:42:29 +0100
Subject: [PATCH] [GFS2] Remove ail2 list from the ai
The ail2 list wasn't
It looks to me like configure should be setting the default sbindir to
{prefix}/usr/sbin instead of {prefix}/sbin.
As it is now, using openais DESTDIR=/ and the default cluster/configure
settings, aisexec is installed to /usr/sbin/aisexec but cman_tool looks
for it in /sbin/aisexec and fails.
configure was recently changed from a default of -O0 to -O2. A couple of
places in the tree also use -Werror. The new combination of -O2 and
-Werror breaks the build when using default configure setting.
[using gcc (GCC) 4.1.2 20070626 (Red Hat 4.1.2-13)]
We need to remove the -Werror's, go
On Thu, Sep 06, 2007 at 08:36:25PM +0200, Fabio Massimo Di Nitto wrote:
David Teigland wrote:
It looks to me like configure should be setting the default sbindir to
{prefix}/usr/sbin instead of {prefix}/sbin.
As it is now, using openais DESTDIR=/ and the default cluster/configure
On Thu, Sep 13, 2007 at 11:04:43PM -0500, Bob Peterson wrote:
diff -pur a/fs/gfs2/locking/dlm/thread.c b/fs/gfs2/locking/dlm/thread.c
--- a/fs/gfs2/locking/dlm/thread.c2007-09-13 17:33:58.0 -0500
+++ b/fs/gfs2/locking/dlm/thread.c2007-09-13 22:47:14.0 -0500
@@ -279,8
versa. Races are avoided by blocking dlm_recv when
setting the flag that switches between modes.
Signed-off-by: David Teigland [EMAIL PROTECTED]
---
diff --git a/fs/dlm/dlm_internal.h b/fs/dlm/dlm_internal.h
index 74901e9..d2fc238 100644
--- a/fs/dlm/dlm_internal.h
+++ b/fs/dlm/dlm_internal.h
On Tue, Sep 18, 2007 at 04:40:45PM -0500, David Teigland wrote:
I believe the time has arrived for a STABLE2 cluster branch.
CVS HEAD hasn't been usable by most people for quite a while, partly due
to ugly build requirements and partly due to instability of new code.
Building HEAD currently
On Fri, Nov 02, 2007 at 09:37:15AM -0500, Bob Peterson wrote:
Hi,
This patch changes the /sys/fs/gfs2/s_id/id file to give the device
id major:minor rather than the s_id. That enables gfs2_tool to
match devices properly (by id, not name) when locating the tuning files.
We have to be
On Sat, Nov 03, 2007 at 01:04:30AM +0100, Adrian Bunk wrote:
This patch adds a proper prototype for some functions in
fs/dlm/dlm_internal.h
Acked-by: David Teigland [EMAIL PROTECTED]
Signed-off-by: Adrian Bunk [EMAIL PROTECTED]
---
fs/dlm/dlm_internal.h | 16
fs
Use wait_event_interruptible() in the lock_dlm thread instead
of an open coded equivalent, and include a kthread_should_stop()
check in the wait test so we don't miss a kthread_stop().
Signed-off-by: David Teigland [EMAIL PROTECTED]
---
fs/gfs2/locking/dlm/thread.c |9 ++---
1 files
The dlm functions in memory.c should use the dlm_ prefix. Also, use
kzalloc/kfree directly for dlm_direntry's, removing the wrapper functions.
Signed-off-by: David Teigland [EMAIL PROTECTED]
---
fs/dlm/dir.c | 10 +-
fs/dlm/lock.c | 26 +-
fs/dlm
Change log_error() to log_debug() for conditions that can occur in
large number in normal operation.
Signed-off-by: David Teigland [EMAIL PROTECTED]
---
fs/dlm/lock.c |2 +-
1 files changed, 1 insertions(+), 1 deletions(-)
diff --git a/fs/dlm/lock.c b/fs/dlm/lock.c
index 3915b8e..c21deba
Print error with log_error() to be consistent with others.
Signed-off-by: David Teigland [EMAIL PROTECTED]
---
fs/gfs2/locking/dlm/mount.c |3 +--
1 files changed, 1 insertions(+), 2 deletions(-)
diff --git a/fs/gfs2/locking/dlm/mount.c b/fs/gfs2/locking/dlm/mount.c
index ab30102..f2efff4
On Wed, Nov 21, 2007 at 05:50:16PM -, [EMAIL PROTECTED] wrote:
CVSROOT: /cvs/cluster
Module name: cluster
Branch: RHEL5
Changes by: [EMAIL PROTECTED] 2007-11-21 17:50:16
Modified files:
group/gfs_controld: lock_dlm.h
Log message:
ASSERT was doing
The fl_owner is that of lockd when posix locks arrive from nfs
clients, so it can't be used to distinguish between lock holders.
Use fl_pid as owner instead; it's the pid of the process on the
nfs client.
Signed-off-by: David Teigland [EMAIL PROTECTED]
---
fs/gfs2/locking/dlm/plock.c | 18
Hi Steven,
you can try to pull from here:
git pull git://git.fugedabout.it/people/fabbione/gfs2-2.6-nmw.git
[DLM] Fix endian issue when transmitting or receiving LOCK_REPLY
[DLM] align static buffer
gitweb:
http://git.fugedabout.it/?p=people/fabbione/gfs2-2.6-nmw.git;a=summary
On Sat, Jan 19, 2008 at 06:58:17AM +0100, Fabio M. Di Nitto wrote:
Hi guys,
in certain situations where gfs2 init scripts are not used to umount gfs2
volume, we endup with umount.gfs2 being invoked with -r option and this
fails because we don't know what to do with this option.
The
This is the current set of dlm patches that I'm collecting at
http://people.redhat.com/teigland/dlm-patches-testing/
I'm preparing to send these upstream for 2.6.25 in the next week
or so, depending on review and testing. They come mainly from
- the mixed architecture testing and fixing that
all
objects
and the DLM cannot be restarted without a system reboot.
See bz#428119
Signed-off-by: Patrick Caulfield [EMAIL PROTECTED]
Signed-off-by: Fabio M. Di Nitto [EMAIL PROTECTED]
Signed-off-by: David Teigland [EMAIL PROTECTED]
---
fs/dlm/lowcomms.c |2 ++
1 files changed, 2 insertions
From: Adrian Bunk [EMAIL PROTECTED]
This patch adds a proper prototype for some functions in
fs/dlm/dlm_internal.h
Signed-off-by: Adrian Bunk [EMAIL PROTECTED]
Signed-off-by: David Teigland [EMAIL PROTECTED]
---
fs/dlm/dlm_internal.h | 16
fs/dlm/lock.c |1 -
fs
Change log_error() to log_debug() for conditions that can occur in
large number in normal operation.
Signed-off-by: David Teigland [EMAIL PROTECTED]
---
fs/dlm/lock.c |2 +-
1 files changed, 1 insertions(+), 1 deletions(-)
diff --git a/fs/dlm/lock.c b/fs/dlm/lock.c
index 7bc6ad9..63fe74d
the platform-specific ones at the other end.
Many thanks to Fabio for testing this patch.
Initial patch from Patrick.
Signed-off-by: Patrick Caulfield [EMAIL PROTECTED]
Signed-off-by: Fabio M. Di Nitto [EMAIL PROTECTED]
Signed-off-by: David Teigland [EMAIL PROTECTED]
---
fs/dlm/util.c | 57
From: Fabio M. Di Nitto [EMAIL PROTECTED]
DLM_RCOM_LOCK_REPLY messages need byte swapping.
Signed-off-by: Fabio M. Di Nitto [EMAIL PROTECTED]
Signed-off-by: David Teigland [EMAIL PROTECTED]
---
fs/dlm/util.c |9 ++---
1 files changed, 6 insertions(+), 3 deletions(-)
diff --git a/fs/dlm
to fix their systems or use clever routing
tricks.
Signed-off-by: Lon Hohberger [EMAIL PROTECTED]
Signed-off-by: Patrick Caulfield [EMAIL PROTECTED]
Signed-off-by: David Teigland [EMAIL PROTECTED]
---
fs/dlm/lowcomms.c | 13 -
1 files changed, 12 insertions(+), 1 deletions(-)
diff --git
time.
Appears when process calls libdlm dlm_release_lockspace() which first
closes the ls dev triggering clear_proc_locks, and then removes the ls
(a write to control dev) causing release_lockspace().
Signed-off-by: David Teigland [EMAIL PROTECTED]
---
fs/dlm/lock.c |1 +
1 files changed, 1
start doing recovery in the presence of a many overlapping
unlock/cancel ops.
Signed-off-by: David Teigland [EMAIL PROTECTED]
---
fs/dlm/lock.c | 37 -
1 files changed, 32 insertions(+), 5 deletions(-)
diff --git a/fs/dlm/lock.c b/fs/dlm/lock.c
index 43ca2a3
When a failed request (EBADR or ENOTBLK) is unlocked/canceled instead of
retried, there may be other lkb's waiting on the rsb_lookup list for it
to complete. A call to confirm_master() is needed to move on to the next
waiting lkb since the current one won't be retried.
Signed-off-by: David
, the infinite loop is dangerous since some other
unknown condition may appear causing the loop to never break.
Signed-off-by: David Teigland [EMAIL PROTECTED]
---
fs/dlm/lock.c |6 --
1 files changed, 4 insertions(+), 2 deletions(-)
diff --git a/fs/dlm/lock.c b/fs/dlm/lock.c
index fa68e9b
The invalid lockspace messages are normal and can appear relatively
often. They should be suppressed without debugging enabled.
Signed-off-by: David Teigland [EMAIL PROTECTED]
---
fs/dlm/lock.c |5 +++--
1 files changed, 3 insertions(+), 2 deletions(-)
diff --git a/fs/dlm/lock.c b/fs/dlm
I've sent a second batch of dlm patches to lkml for review prior to
another pull request for 2.6.25, beginning here:
http://lkml.org/lkml/2008/2/7/10
They are also in the test branch of dlm.git:
http://git.kernel.org/gitweb.cgi?p=linux/kernel/git/teigland/dlm.git;a=shortlog;h=test
On Wed, Feb 13, 2008 at 11:29:38PM +0200, Adrian Bunk wrote:
dlm_print_rsb() can now become static.
Signed-off-by: Adrian Bunk [EMAIL PROTECTED]
Thanks, added to dlm.git.
Dave
On Sat, Mar 01, 2008 at 02:52:05PM -0700, Steven Dake wrote:
This is reasonable but requires having quite a bit of conditional
compilation in cman and other tools. I don't know if anyone is working
on this, but I'd imagine maintenance of such a scheme would be
complicated since the trunk of
On Mon, Mar 03, 2008 at 05:10:54PM +0100, Fabio M. Di Nitto wrote:
If we are to say this conditional compilation only works with trunk of
openais up to a certain point such as version 0.84 then that certain
point becomes a branch point which I really do not want. What I
prefer is that trunk
On Mon, Mar 03, 2008 at 10:07:26AM -0700, Steven Dake wrote:
On Mon, 2008-03-03 at 09:10 -0600, David Teigland wrote:
On Sat, Mar 01, 2008 at 02:52:05PM -0700, Steven Dake wrote:
This is reasonable but requires having quite a bit of conditional
compilation in cman and other tools. I
I've gone and looked at the cluster.git history and realize that we're not
using git quite as we should. We're polluting the cluster.git history
with unnecessary merge commits. It's not that git is being used wrongly
per se, just not nicely. Not to blame anyone, but pull up git web in
your
On Tue, Mar 11, 2008 at 03:24:24PM +0100, Kadlecsik Jozsef wrote:
On Thu, 6 Mar 2008, David Teigland wrote:
A new source tarball of cluster code has been released: cluster-2.02.00
Is there a changelog available somewhere? I could not find it in the
tarball.
No, sorry, I wish
On Wed, Mar 19, 2008 at 03:35:11PM -0700, Joel Becker wrote:
Folks,
Another problem I've run into with libdlm - call
dlm_ls_lock_wait() on a lock that another node holds, and it returns
instead of blocking. This is not a trylock (LKF_NOQUEUE). Trylocks
work as expected. A blocking
work properly.
Christine Caulfield (5):
[DLM] Don't segfault if lvbptr is NULL
[CMAN] Free up any queued messages when someone disconnects
[CMAN] Limit outstanding replies
[CMAN] valid port number don't use it before validation
Remove references to broadcast.
David
On Sun, Apr 13, 2008 at 01:56:12PM +0200, Fabio M. Di Nitto wrote:
On Fri, 11 Apr 2008, David Teigland wrote:
A new source tarball of cluster code has been released: cluster-2.03.00
This has been taken from the STABLE2 branch in the cluster git tree. It
is compatible with the current stable
On Fri, Apr 11, 2008 at 04:29:52PM -, [EMAIL PROTECTED] wrote:
- Log -
commit 77bce77b5034adf8f00090b13dde7c7d481b0dd9
Author: David Teigland [EMAIL PROTECTED]
Date: Wed Mar 19 16:05:20 2008 -0500
dlm_controld: new
type in argument 3 (different
signedness)
fs/dlm/config.c:149:1:expected unsigned int *info_field
fs/dlm/config.c:149:1:got int extern [toplevel] *noident
Signed-off-by: Harvey Harrison [EMAIL PROTECTED]
Signed-off-by: David Teigland [EMAIL PROTECTED]
---
fs/dlm/config.c |2 +-
1
From: Adrian Bunk [EMAIL PROTECTED]
dlm_print_rsb() can now become static.
Signed-off-by: Adrian Bunk [EMAIL PROTECTED]
Signed-off-by: David Teigland [EMAIL PROTECTED]
---
fs/dlm/lock.c |2 +-
fs/dlm/lock.h |1 -
2 files changed, 1 insertions(+), 2 deletions(-)
diff --git a/fs/dlm
is already in the member list.
Signed-off-by: David Teigland [EMAIL PROTECTED]
---
fs/dlm/config.c | 48 +++-
fs/dlm/config.h |3 ++-
fs/dlm/dlm_internal.h |4 +++-
fs/dlm/member.c | 34 +-
fs/dlm
On Wed, Apr 16, 2008 at 08:35:57AM -0500, David Teigland wrote:
On Wed, Apr 16, 2008 at 05:53:43AM +0200, Fabio M. Di Nitto wrote:
On Tue, 15 Apr 2008, David Teigland wrote:
On Tue, Apr 15, 2008 at 04:02:26PM -0500, David Teigland wrote:
Move the code that handles cluster posix locks
On Tue, May 13, 2008 at 09:01:13PM +0100, Steven Whitehouse wrote:
Hi,
It might be a silly question, but this looks to me like trying to fix a
kernel bug by adding a userland one. Why not simply update the kernel to
return the correct value?
Yes, there's already a kernel fix in dlm.git, see
On Wed, May 14, 2008 at 09:56:11AM +0100, Steven Whitehouse wrote:
Hi,
On Tue, 2008-05-13 at 15:13 -0500, David Teigland wrote:
On Tue, May 13, 2008 at 09:01:13PM +0100, Steven Whitehouse wrote:
Hi,
It might be a silly question, but this looks to me like trying to fix a
kernel
On Wed, May 28, 2008 at 02:45:10PM +0900, Masatake YAMATO wrote:
Hi,
I found a way to let linux dereference NULL pointer
in gfs2-2.6-nmw/fs/dlm/user.c.
If `device_write' method is called via dlm-control,
file-private_data is NULL. (See ctl_device_open() in
user.c. ) Through proc-flags
On Fri, May 30, 2008 at 05:36:41PM -0700, Joel Becker wrote:
We have determined that ocfs2 can only leave a cluster group safely in
put_super(7). The presence of bind mounts, rbind mounts, and shared
subtrees make tracking mountpoints impossible in userspace.
To solve this, we move the
On Tue, Jun 03, 2008 at 08:55:49AM +0200, Fabio M. Di Nitto wrote:
On Mon, 2 Jun 2008, Joel Becker wrote:
On Tue, Jun 03, 2008 at 05:57:35AM -, [EMAIL PROTECTED] wrote:
commit e879971090c6821bb966f17875874d11aa740a5c
Author: Fabio M. Di Nitto [EMAIL PROTECTED]
Date: Tue Jun 3 07:54:37
It seems there's been some confusion about what the config system (ccs
replacement) should be and do in cluster3. There were just two ideas I
offered way back at the beginning:
1. Move the update mechanism outside the config system.
2. What remains is the part that reads the local cluster.conf
On Wed, Jun 25, 2008 at 06:19:00PM +0200, Fabio M. Di Nitto wrote:
. Leave log_debug() unchanged,
The only change is that it uses logsys to print instead fprintf to stderr.
Like Christine already pointed out, the change to logsys is to have log
output the same across the whole system. No
On Fri, Jun 27, 2008 at 08:19:36PM +0200, Fabio M. Di Nitto wrote:
I was actually hoping that with no more ccsd there'd be no more
connecting to ccs, but that's probably a topic for one of the ccs
meetings...
The only partial advantage you have, as i documented and wrote to
cluster-devel,
Main points from the logsys discussion we had
- initialization: use functions instead of macros, don't always need
logging to be working from the start of execution, can wait until
function is called to start it, don't need notion of subsystems
or per-source-file logging features
-
On Mon, Jun 30, 2008 at 07:59:14PM +0300, Benny Halevy wrote:
gcc 4.3.0 correctly emits the following warning.
search_rsb_list does not *r_ret if no dlm_rsb is found
and _search_rsb may pass the uninitialized value upstream
on the error path when both calls to search_rsb_list
return non-zero
On Mon, Jun 30, 2008 at 06:38:48PM +0200, Fabio M. Di Nitto wrote:
On Mon, 30 Jun 2008, David Teigland wrote:
- configuration setup: big blocks of setup code are repeated and largely
the same, make this less
I will take care of this bit since i already done it.
the api will look like
On Tue, Jul 01, 2008 at 07:01:42AM +0200, Fabio M. Di Nitto wrote:
No. You can just install the callback and be done with it. The ccs fd was
never a real fd to poll.
OK, it's a cman callback. If the ccs connection isn't really a
connection and if it's not necessary then can we get rid of the
On Tue, Jul 01, 2008 at 12:21:21PM -0500, David Teigland wrote:
(What doesn't work yet is the test 1 output
following the logsys_init() call.)
was missing logsys_flush()
+int logsys_init(char *name, int mode, int facility, int priority, char *file)
+{
+ char *errstr;
Thinking about
setup uses cman_is_active
- cman setup retries cman_init and cman_is_active
Signed-off-by: David Teigland [EMAIL PROTECTED]
diff --git a/fence/fenced/Makefile b/fence/fenced/Makefile
index 1e9bbc9..61ec989 100644
--- a/fence/fenced/Makefile
+++ b/fence/fenced/Makefile
@@ -15,7 +15,8
On Wed, Jul 02, 2008 at 06:31:10AM +0200, Fabio M. Di Nitto wrote:
@@ -9,18 +11,62 @@ static int open_ccs(void)
sleep(1);
if (++i 9 !(i % 10))
log_error(connect to ccs error %d,
- check ccsd or cluster status, cd);
On Wed, Jul 02, 2008 at 10:49:05AM -0500, David Teigland wrote:
#define DEFAULT_FILE LOGDIR /fenced.log
LOGDIR is set by the build system (same reasons as SYSLOGFACILITY). We
want files by default consistently across the board.
I think that by default we should probably have all
On Wed, Jul 02, 2008 at 08:22:54PM +0200, Fabio M. Di Nitto wrote:
I was thinking about the error
messages we're switching from syslog to logsys. So, how do we tell logsys
to use /var/log/messages for errors and a separate file for debug output?
Why do you need this? Remember that you are
We're planning to move the cluster git tree to fedorahosted.org, to take
advantage of the CLA system in place there. To push changes to the new
git tree you'll need to:
- Set up an account at https://admin.fedoraproject.org/accounts/user/new
- Sign the CLA on your new account page
- Request
On Mon, Jul 28, 2008 at 10:20:49AM +0200, Fabio M. Di Nitto wrote:
Hi guys,
I just noticed that we have a very inconsistent way to set init script
defaults by using /etc/sysconfig/{cman,cluster,scsi_reserve}.
the patch in attachment is very simple and standardize everything to
On Wed, Oct 29, 2008 at 11:12:41AM -0500, Kevin Anderson wrote:
Hi all,
Recently we had cluster customer where the fencing agent successfully
powered off a node, but the script failed to power the node back on due
to firmware changes on the fencing device.
Question is whether we should
On Thu, Oct 30, 2008 at 07:20:21PM +0100, Fabio M. Di Nitto wrote:
a,b,c,x,y,z are connections that are all *controlled independently*
a is always on
b is always on
c is connected if debug=on
x is connected if to_stderr=yes
y is connected if to_syslog=yes
z is connected if to_file=yes
On Thu, Oct 30, 2008 at 11:26:14PM -0700, Steven Dake wrote:
There are two types of messages. Those intended for users/admins and
those intended for developers.
Both of these message types should always be recorded *somewhere*. The
entire concept of LOG_LEVEL_DEBUG is dubious to me. If
On Tue, Nov 04, 2008 at 02:58:47PM -0600, David Teigland wrote:
the cluster.conf logging/ section? My suggestion is:
syslog_level=foo
logfile_level=bar
FWIW, I'm not set on this if someone has a better suggestion. I just want
something unambiguous. debug=on has been shown to mean
On Mon, Nov 10, 2008 at 08:09:10PM +0100, Fabio M. Di Nitto wrote:
Hi all,
those logging threads have been going on for way too long. It's time to
close them and make a final decision. This is a long email, so please
take time to read it all.
This is a recap of what I believe a user would
On Thu, Nov 13, 2008 at 09:56:18AM +, Steven Whitehouse wrote:
It is left as an exercise for the reader to consider whether its a bug
that DLM isn't using highmem pages for its internal buffers (in which
case we'd have to solve the allocation problem at kmap time), or whether
its a bug
On Fri, Nov 14, 2008 at 10:18:13AM +0100, Fabio M. Di Nitto wrote:
At this point we haven't really settled how many (sub) project will be
created out of this split. This will come once we agree how to split.
I like the third option as long as the number of new git trees doesn't
explode
On Fri, Nov 14, 2008 at 10:11:00PM +0100, Andrew Beekhof wrote:
I'd have thought fence.git and fence-agents.git in one and cman.git
and rgmanager.git in another.
But I may be missing some of the interdependencies.
I wouldn't mind either of those combinations. Maybe rgmanager's last
stand will
On Thu, Nov 27, 2008 at 10:45:21AM +, Steven Whitehouse wrote:
From 04b985e291c464092516d0d1a4387b866389a85d Mon Sep 17 00:00:00 2001
From: Steven Whitehouse [EMAIL PROTECTED]
Date: Thu, 27 Nov 2008 09:42:51 +
Subject: [PATCH] GFS2: Send useful information with uevent messages
In
On Fri, Nov 28, 2008 at 11:07:56AM +, Steven Whitehouse wrote:
LOCKTABLE=clustername:fsname
LOCKPROTO=[lock_dlm|lock_nolock]
to avoid all the messy parsing of the initial event string. Also I've
added come further information to the two change events, so that we
now have:
Here are the compatibility aspects to the recent ideas about changes to
the user/kernel interface between gfs (1 2) and gfs_controld.
. gfs_controld can remove id from hostdata string in mount options
- no compat issues AFAICT
. getting rid of id sysfs file from lock_dlm
- new
On Thu, Dec 04, 2008 at 01:32:31PM -0500, david m. richter wrote:
On Mon, Dec 1, 2008 at 12:31 PM, David Teigland [EMAIL PROTECTED] wrote:
Here are the compatibility aspects to the recent ideas about changes to
the user/kernel interface between gfs (1 2) and gfs_controld.
. gfs_controld
On Fri, Dec 05, 2008 at 09:51:45AM +, Steven Whitehouse wrote:
In that case gfs2 should be able to generate the id itself from the
fsname and it still doesn't need it passed in, even if it continues to
expose the id in sysfs.
Perhaps better still, it should be possible for David to
On Fri, Dec 05, 2008 at 08:52:58AM -0600, David Teigland wrote:
On Fri, Dec 05, 2008 at 09:51:45AM +, Steven Whitehouse wrote:
In that case gfs2 should be able to generate the id itself from the
fsname and it still doesn't need it passed in, even if it continues to
expose the id
On Mon, Dec 22, 2008 at 09:22:56AM +, Steven Whitehouse wrote:
Cleans code up.
Might be wrong.
This is an O(n*n) search :(
Thats true, but for fairly low values of n in general. Also the dlm
locking will only be stopped for a lockspace in the case that we are in
recovery, so
On Wed, Jan 21, 2009 at 06:42:39PM -0500, J. Bruce Fields wrote:
On Wed, Jan 21, 2009 at 11:34:50AM -0500, Jeff Layton wrote:
dlm_posix_get fills out the relevant fields in the file_lock before
returning when there is a lock conflict, but doesn't clean out any of
the other fields in the
On Tue, Jan 27, 2009 at 02:06:30PM -0600, David Teigland wrote:
On Tue, Jan 27, 2009 at 11:33:30AM +, Chrissie Caulfield wrote:
This an updated patch that uses hlists rather than list_heads to save
memory in the connection structure.
Thanks to Steven Whitehouse for the suggestion
I have a suggestion to improve our logging config. The format below is the
default configuration (more or less, the corosync systems aren't sending
anything to syslog, but cman.log seems full of info-like stuff, but it's
beside the point):
logging to_syslog=yes to_logfile=yes
On Fri, Feb 20, 2009 at 10:00:03AM -0600, David Teigland wrote:
I suggest the following, notice the final corosync entry,
logging to_syslog=yes to_logfile=yes syslog_facility=daemon
syslog_priority=info logfile_priority=info
logging_daemon=qdiskd
On Mon, Feb 23, 2009 at 07:52:55PM +0100, Fabio M. Di Nitto wrote:
A node unfences *itself* when it boots up. As such, power-unfencing doesn't
make sense; unfencing is only meant to reverse storage fencing.
What can stop a user to run fence_node -U from another node to do remote
On Mon, Feb 23, 2009 at 01:36:04PM -0600, Ryan O'Hara wrote:
What happens if unfencing fails? Is it safe to say that a node that
fails to unfence itself will be prohibited from joining the fence
domain? This is important for fence_scsi, since unfencing is
equivalient to re-registering with the
On Mon, Feb 23, 2009 at 02:24:13PM -0600, Ryan O'Hara wrote:
On Mon, Feb 23, 2009 at 01:09:58PM -0600, David Teigland wrote:
On Mon, Feb 23, 2009 at 07:52:55PM +0100, Fabio M. Di Nitto wrote:
What can stop a user to run fence_node -U from another node to do remote
(un)fencing
On Thu, Feb 26, 2009 at 07:51:57AM +0100, Fabio M. Di Nitto wrote:
On Mon, 2009-02-23 at 13:09 -0600, David Teigland wrote:
On Mon, Feb 23, 2009 at 07:52:55PM +0100, Fabio M. Di Nitto wrote:
A node unfences *itself* when it boots up. As such, power-unfencing
doesn't
make sense
On Wed, Jan 28, 2009 at 11:27:35AM +, Chrissie Caulfield wrote:
David Teigland wrote:
On Tue, Jan 27, 2009 at 02:06:30PM -0600, David Teigland wrote:
On Tue, Jan 27, 2009 at 11:33:30AM +, Chrissie Caulfield wrote:
This an updated patch that uses hlists rather than list_heads to save
From: Joe Perches j...@perches.com
Signed-off-by: Joe Perches j...@perches.com
Signed-off-by: David Teigland teigl...@redhat.com
---
fs/dlm/lowcomms.c |4 ++--
1 files changed, 2 insertions(+), 2 deletions(-)
diff --git a/fs/dlm/lowcomms.c b/fs/dlm/lowcomms.c
index 103a5eb..bf09262 100644
From: Christine Caulfield ccaul...@redhat.com
Integer nodeids can be too large for the idr code; use a hash
table instead.
Signed-off-by: Christine Caulfield ccaul...@redhat.com
Signed-off-by: David Teigland teigl...@redhat.com
---
fs/dlm/lowcomms.c | 171
From: Steven Whitehouse swhit...@redhat.com
The ls_dirtbl[].lock was an rwlock, but since it was only used in write
mode a spinlock will suffice.
Signed-off-by: Steven Whitehouse swhit...@redhat.com
Signed-off-by: David Teigland teigl...@redhat.com
---
fs/dlm/dir.c | 18
Return immediately from dlm_unlock(CANCEL) if the lock is
granted and not being converted; there's nothing to cancel.
Signed-off-by: David Teigland teigl...@redhat.com
---
fs/dlm/lock.c |7 +++
1 files changed, 7 insertions(+), 0 deletions(-)
diff --git a/fs/dlm/lock.c b/fs/dlm/lock.c
On Thu, Mar 26, 2009 at 02:50:31PM +0100, Fabio M. Di Nitto wrote:
In our current startup sequence, we do start a daemon, we make sure it
starts, but we never check if it's actually working properly.
If there's no groupd_compat setting in cluster.conf, or if it's set to 2, then
groupd does
On Tue, Mar 31, 2009 at 07:23:15AM +0200, Fabio M. Di Nitto wrote:
On Mon, 2009-03-30 at 16:42 -0500, David Teigland wrote:
On Thu, Mar 26, 2009 at 02:50:31PM +0100, Fabio M. Di Nitto wrote:
In our current startup sequence, we do start a daemon, we make sure it
starts, but we never check
On Thu, May 07, 2009 at 03:29:03PM +0100, Chrissie Caulfield wrote:
If you do
# dlm_tool lockdump default
on a lockspace with no locks in it, you get the error message:
can't read /sys/kernel/debug/dlm/default_locks: Success
This patch puts a slightly more sensible error message
/dlm/lowcomms.h |3 ++-
fs/dlm/member.c | 19 +--
fs/dlm/requestqueue.c |2 +-
include/linux/dlm.h |4 ++--
7 files changed, 48 insertions(+), 26 deletions(-)
Christine Caulfield (1):
dlm: connect to nodes earlier
David Teigland (2):
dlm: fix
When a lockspace was joined multiple times, the global dlm
use count was incremented when it should not have been. This
caused the global dlm threads to not be stopped when all
lockspaces were eventually be removed.
Signed-off-by: David Teigland teigl...@redhat.com
---
fs/dlm/lockspace.c | 13
Change some GFP_KERNEL allocations to use either GFP_NOFS or
ls_allocation (when available) which the fs sets to GFP_NOFS.
The point is to prevent allocations from going back into the
cluster fs in places where that might lead to deadlock.
Signed-off-by: David Teigland teigl...@redhat.com
---
fs
From: Geert Uytterhoeven ge...@linux-m68k.org
| fs/gfs2/lock_dlm.c:207: warning: passing argument 1 of 'dlm_new_lockspace'
discards qualifiers from pointer target type
Signed-off-by: Geert Uytterhoeven ge...@linux-m68k.org
Signed-off-by: David Teigland teigl...@redhat.com
---
fs/dlm
1 - 100 of 341 matches
Mail list logo
