From: David Teigland <teigland@redhat.com>
To: cluster-devel.redhat.com
Subject: [Cluster-devel] GFS2 and uevents document
Date: Thu, 13 Aug 2009 11:02:02 -0500 [thread overview]
Message-ID: <20090813160202.GB8148@redhat.com> (raw)
In-Reply-To: <1250175480.3438.4.camel@localhost.localdomain>
On Thu, Aug 13, 2009 at 03:58:00PM +0100, Steven Whitehouse wrote:
> 2. ONLINE
>
> The ONLINE uevent is generated after a successful mount or remount. It
> has the same environment variables as the ADD uevent. The ONLINE
> uevent, along with the two environment variables for spectator and
> rdonly are a relatively recent addition (2.6.32-rc+) and will not
> be generated by older kernels.
The standard way to know if a mount is successful is to look at the return
value from mount(2). Is a second way really needed? Will whatever userspace
code that needs the result need to wait for and collect both results? Will
both results always agree? Will the results appear in the same order? For
repeated mount/unmount of the same fs is there a way to match the ONLINE
uevent's to the specific mount call that produced it?
Dave
next prev parent reply other threads:[~2009-08-13 16:02 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-08-13 14:58 [Cluster-devel] GFS2 and uevents document Steven Whitehouse
2009-08-13 16:02 ` David Teigland [this message]
2009-08-13 17:14 ` Steven Whitehouse
[not found] <354693629.557911250176397806.JavaMail.root@zmail06.collab.prod.int.phx2.redhat.com>
2009-08-13 15:13 ` Bob Peterson
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=20090813160202.GB8148@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).