From: David Teigland <teigland@redhat.com>
To: cluster-devel.redhat.com
Subject: [Cluster-devel] GFS2: Send useful information with uevent messages
Date: Mon, 1 Dec 2008 09:25:31 -0600 [thread overview]
Message-ID: <20081201152531.GB24608@redhat.com> (raw)
In-Reply-To: <1227782721.9571.134.camel@quoit>
On Thu, Nov 27, 2008 at 10:45:21AM +0000, Steven Whitehouse wrote:
> >From 04b985e291c464092516d0d1a4387b866389a85d Mon Sep 17 00:00:00 2001
> From: Steven Whitehouse <swhiteho@redhat.com>
> Date: Thu, 27 Nov 2008 09:42:51 +0000
> Subject: [PATCH] GFS2: Send useful information with uevent messages
>
> In order to distinguish between two differing uevent messages
> and to avoid using the (racy) method of reading status from
> sysfs in future, this adds some status information to our
> uevent messages.
>
> Btw, before anybody says "sysfs isn't racy", I'm aware of that,
> but the way that GFS2 was using it (send an ambiugous uevent and
> then expect the receiver to read sysfs to find out the status
> of the reported operation) was.
Not as long as gfs_controld tells gfs-kernel to recover journals one at a
time on a node, which is what it does to avoid this problem.
next prev parent reply other threads:[~2008-12-01 15:25 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-11-27 10:45 [Cluster-devel] GFS2: Send useful information with uevent messages Steven Whitehouse
2008-12-01 15:25 ` David Teigland [this message]
2008-12-01 15:37 ` Steven Whitehouse
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20081201152531.GB24608@redhat.com \
--to=teigland@redhat.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.