From: Bob Peterson <rpeterso@redhat.com>
To: cluster-devel.redhat.com
Subject: [Cluster-devel] [GFS2 PATCH] GFS2: Log the reason for log flushes in every log header
Date: Mon, 11 Dec 2017 08:23:17 -0500 (EST) [thread overview]
Message-ID: <671649677.40445923.1512998597014.JavaMail.zimbra@redhat.com> (raw)
In-Reply-To: <5adc2737-1f11-27b1-eb46-733fdd9ab9df@redhat.com>
Hi,
----- Original Message -----
| > + LHF_SHUTDOWN = 0,
| Should 0 be used for "unknown"?
Good idea. I'll add that.
(snip)
| > + /* Constants reserved for user space / gfs2-utils */
| > + LHF_GFS2_CONVERT = 26,
| > + LHF_GFS2_EDIT = 27,
| > + LHF_GFS2_FSCK = 28,
| > + LHF_GFS2_FSCK_JREPLAY = 29,
| > + LHF_GFS2_MKFS = 30,
| > + LHF_GFS2_JADD = 31
|
| Would it be better to have values for the purposes that the utils would
| need to touch the log header, e.g. LHF_UTIL_REPLAY, LHF_UTIL_FIX or
| LHF_UTIL_CREATE. That way, if a util is renamed or a new util is written
| (even some third party tool that we don't know about) they would still
| have a sensible value to use.
|
| Cheers,
| Andy
Actually, yes, I was kind of hoping you would suggest some useful
values for user space. I didn't go over how gfs2-utils works with log
headers because I didn't want to delay posting a prototype further.
I only allocated one 32-bit set of flags, with some space in the middle
carved out for user space, but it seems a bit confining. Obviously this
is still just a prototype, so we can add another 32-bit flag (one for
kernel space and one for user space?) or improve it any other way that
would be useful. I'm open to suggestions.
Regards,
Bob Peterson
Red Hat File Systems
next prev parent reply other threads:[~2017-12-11 13:23 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1917016702.37199765.1512156875142.JavaMail.zimbra@redhat.com>
2017-12-01 19:34 ` [Cluster-devel] [GFS2 PATCH] GFS2: Log the reason for log flushes in every log header Bob Peterson
2017-12-04 12:12 ` Steven Whitehouse
2017-12-08 15:30 ` Bob Peterson
2017-12-11 11:53 ` Andrew Price
2017-12-11 12:12 ` Steven Whitehouse
2017-12-11 13:23 ` Bob Peterson [this message]
2017-12-11 15:32 ` Andrew Price
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=671649677.40445923.1512998597014.JavaMail.zimbra@redhat.com \
--to=rpeterso@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.