All of lore.kernel.org
 help / color / mirror / Atom feed
From: Coly Li <coly.li@suse.de>
To: ocfs2-devel@oss.oracle.com
Subject: [Ocfs2-devel] [PATCH] ocfs2: return f_fsid info in ocfs2_statfs()
Date: Fri, 16 Jan 2009 17:19:43 +0800	[thread overview]
Message-ID: <4970512F.6040009@suse.de> (raw)
In-Reply-To: <496F95A8.3030404@oracle.com>



Sunil Mushran Wrote:
> It's worse. As far as I can see, the s_uuid_hash is never populated.
> So we have two problems. The second issue is urgent as we are
> using it in xattr.
> 
Thanks for pointing out this :)
I have updated the patch and sent out as v4.

> Coly Li wrote:
>> Sunil Mushran Wrote:
>>  
>>> Wondering whether this id needs to be endian consistent.
>>> For failover nfs setups maybe.
>>>     
>>
>> IMHO, It is. Because osb->uuid_hash is fetched by:
>>         osb->uuid_hash = le32_to_cpu(di->id2.i_super.s_uuid_hash);
>> CMIIW, It should work in nfs failover.
>>
>>  
[snip]
-- 
Coly Li
SuSE Labs

      parent reply	other threads:[~2009-01-16  9:19 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
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 [this message]

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=4970512F.6040009@suse.de \
    --to=coly.li@suse.de \
    --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.