All of lore.kernel.org
 help / color / mirror / Atom feed
From: David Teigland <teigland@redhat.com>
To: cluster-devel.redhat.com
Subject: [Cluster-devel] gfs uevent and sysfs changes
Date: Fri, 5 Dec 2008 09:03:23 -0600	[thread overview]
Message-ID: <20081205150323.GB3734@redhat.com> (raw)
In-Reply-To: <20081205145258.GA3734@redhat.com>

On Fri, Dec 05, 2008 at 08:52:58AM -0600, David Teigland wrote:
> On Fri, Dec 05, 2008 at 09:51:45AM +0000, Steven Whitehouse wrote:
> > In that case gfs2 should be able to generate the id itself from the
> > fsname and it still doesn't need it passed in, even if it continues to
> > expose the id in sysfs.
> > 
> > Perhaps better still, it should be possible for David to generate the id
> > directly if he really needs it from the fsname.
> 
> It's not actually a crc of the fsname, but a crc of the cpg name
> gfs_controld creates for the mountgroup, which is "gfs:mount:<fsname>".
> Also, we may at some point want to allow that generated id to be overriden
> by one that's set explicitly.

The fact that this id comes from gfs_controld, and becomes available only
during mount, makes me think it's not well suited to be the statfs fsid.
GFS should probably do it's own thing for statfs (like a hash of just the
fsname) instead of depending on gfs_controld for it.  With nolock the
daemons won't be there, and we'd still want the same fsid to be produced.




  reply	other threads:[~2008-12-05 15:03 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-12-01 17:31 [Cluster-devel] gfs uevent and sysfs changes David Teigland
2008-12-02 14:02 ` Steven Whitehouse
2008-12-04 18:32 ` david m. richter
2008-12-04 21:07   ` David Teigland
2008-12-04 21:59     ` david m. richter
2008-12-04 22:38       ` David Teigland
2008-12-05  9:51         ` Steven Whitehouse
2008-12-05 14:52           ` David Teigland
2008-12-05 15:03             ` David Teigland [this message]
2008-12-05 17:35           ` david m. richter
2008-12-05 17:31         ` david m. richter

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=20081205150323.GB3734@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.