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:
Hi,
On Mon, 2008-12-01 at 09:28 -0600, David Teigland wrote:
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
Hi,
On Mon, 2008-12-01 at 09:25 -0600, David Teigland wrote:
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:
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
