From: Sunil Mushran <sunil.mushran@oracle.com>
To: ocfs2-devel@oss.oracle.com
Subject: [Ocfs2-devel] [PATCH] ocfs2: return f_fsid info in ocfs2_statfs()
Date: Thu, 15 Jan 2009 14:32:07 -0800 [thread overview]
Message-ID: <496FB967.6030708@oracle.com> (raw)
In-Reply-To: <20090115222120.GB17410@wotan.suse.de>
Mark Fasheh wrote:
> Well, mkfs.ocfs2/tunefs.ocfs2 is supposed to populate it s_uuid_hash based
> on the *original* uuid of the file system. We don't dynamically calculate it
> because uuid might change due to a clone operation, which would then break
> the hashing of that particular file system.
OK. I missed that bit.
> Since s_uuid_hash is feature specific, I think perhaps we should just use
> some part of the uuid, which is always populated. For this, I think we could
> do the same as the o2cb dlm key (which has to also be pretty unique) -
> crc32_le(uuid)
I was thinking the same.
next prev parent reply other threads:[~2009-01-15 22:32 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-01-15 19:07 [Ocfs2-devel] [PATCH] ocfs2: return f_fsid info in ocfs2_statfs() Coly Li
2009-01-15 19:25 ` Sunil Mushran
2009-01-15 19:48 ` Coly Li
2009-01-15 19:59 ` Sunil Mushran
2009-01-15 22:21 ` Mark Fasheh
2009-01-15 22:32 ` Sunil Mushran [this message]
2009-01-16 0:17 ` [Ocfs2-devel] Integrating OCFS2 and CLVM Hagmann, Michael
2009-01-16 9:23 ` [Ocfs2-devel] [PATCH] ocfs2: return f_fsid info in ocfs2_statfs() Coly Li
2009-01-16 9:19 ` Coly Li
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=496FB967.6030708@oracle.com \
--to=sunil.mushran@oracle.com \
--cc=ocfs2-devel@oss.oracle.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.