public inbox for cluster-cvs@sourceware.org
help / color / mirror / Atom feed
From: kpreslan@sourceware.org
To: cluster-cvs@sources.redhat.com
Subject: cluster gfs/man/gfs_mount.8 gfs-kernel/src/dlm ...
Date: Fri, 11 Mar 2005 21:46:00 -0000 [thread overview]
Message-ID: <20050311214649.587.qmail@sourceware.org> (raw)
CVSROOT: /cvs/cluster
Module name: cluster
Changes by: kpreslan@sourceware.org 2005-03-11 21:46:49
Modified files:
gfs/man : gfs_mount.8
gfs-kernel/src/dlm: mount.c
gfs-kernel/src/gfs: incore.h lm.c mount.c ops_fstype.c
ops_super.c
gfs-kernel/src/gulm: gulm.h gulm_fs.c
gfs-kernel/src/harness: lm_interface.h main.c
gfs-kernel/src/nolock: main.c
Log message:
Add a new "flags" parameter to lm_mount() of the lock module interface.
When the flag LM_MFLAG_SPECTATOR flag is passed in to the lock module,
GFS is asking to join the filesystem's lockspace, but it doesn't want to
modify the filesystem. The lock module shouldn't assign a journal to the
FS mount. It shouldn't send recovery callbacks to the FS mount. If the
node dies or withdraws, all locks can be wipped immediately.
If the lock module doesn't implement the flag, GFS will work as expected
except that the mount will reserve a journal it will never use.
Add and implement a "spectator" mount option to GFS to take advantage
of the spectator mount flag. When the mount option is used, the FS
looks just like a RO filesystem. The difference is you can have lots and
lots of them.
Patches:
http://sources.redhat.com/cgi-bin/cvsweb.cgi/cluster/gfs/man/gfs_mount.8.diff?cvsroot=cluster&r1=1.4&r2=1.5
http://sources.redhat.com/cgi-bin/cvsweb.cgi/cluster/gfs-kernel/src/dlm/mount.c.diff?cvsroot=cluster&r1=1.13&r2=1.14
http://sources.redhat.com/cgi-bin/cvsweb.cgi/cluster/gfs-kernel/src/gfs/incore.h.diff?cvsroot=cluster&r1=1.19&r2=1.20
http://sources.redhat.com/cgi-bin/cvsweb.cgi/cluster/gfs-kernel/src/gfs/lm.c.diff?cvsroot=cluster&r1=1.5&r2=1.6
http://sources.redhat.com/cgi-bin/cvsweb.cgi/cluster/gfs-kernel/src/gfs/mount.c.diff?cvsroot=cluster&r1=1.10&r2=1.11
http://sources.redhat.com/cgi-bin/cvsweb.cgi/cluster/gfs-kernel/src/gfs/ops_fstype.c.diff?cvsroot=cluster&r1=1.15&r2=1.16
http://sources.redhat.com/cgi-bin/cvsweb.cgi/cluster/gfs-kernel/src/gfs/ops_super.c.diff?cvsroot=cluster&r1=1.14&r2=1.15
http://sources.redhat.com/cgi-bin/cvsweb.cgi/cluster/gfs-kernel/src/gulm/gulm.h.diff?cvsroot=cluster&r1=1.13&r2=1.14
http://sources.redhat.com/cgi-bin/cvsweb.cgi/cluster/gfs-kernel/src/gulm/gulm_fs.c.diff?cvsroot=cluster&r1=1.19&r2=1.20
http://sources.redhat.com/cgi-bin/cvsweb.cgi/cluster/gfs-kernel/src/harness/lm_interface.h.diff?cvsroot=cluster&r1=1.7&r2=1.8
http://sources.redhat.com/cgi-bin/cvsweb.cgi/cluster/gfs-kernel/src/harness/main.c.diff?cvsroot=cluster&r1=1.3&r2=1.4
http://sources.redhat.com/cgi-bin/cvsweb.cgi/cluster/gfs-kernel/src/nolock/main.c.diff?cvsroot=cluster&r1=1.5&r2=1.6
reply other threads:[~2005-03-11 21:46 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=20050311214649.587.qmail@sourceware.org \
--to=kpreslan@sourceware.org \
--cc=cluster-cvs@sources.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 read-only IMAP folder(s) and NNTP newsgroup(s).