All of lore.kernel.org
 help / color / mirror / Atom feed
From: Ian Costello <ianc@sgi.com>
To: Eric Sandeen <sandeen@sandeen.net>
Cc: xfs-oss <xfs@oss.sgi.com>
Subject: Re: [PATCH, RFC] - remove mounpoint UUID code
Date: Sat, 08 Mar 2008 15:40:47 +1100	[thread overview]
Message-ID: <47D218CF.8090909@sgi.com> (raw)
In-Reply-To: <47D2171D.7070202@sandeen.net>

Eric,

My bad, cxfs uses the sb_uuid, should have looked a little closer at the 
patch. I assumed the worst from the heading (must have filtered the 
"point" out of the heading :)

Eric Sandeen wrote:
> Ian Costello wrote:
>> CXFS does use this to mount filesystems, i.e. on a client read the sb 
>> get the uuid and use the uuid to lookup the MDS to request the mount...
> 
> Well, this isn't removing the sb uuid... it's this special file type
> XFS_DINODE_FMT_UUID... which is cxfs using?
> 
> -Eric
> 
>> Having said that if it is removed then it will force us to look at 
>> another method to mount a cxfs filesystem, and also remove the necessity 
>> for cxfs clients to not read the superblock (which is the only metadata 
>> cxfs clients read off disk at this point)...
>>
>> Regards,
>>
> 
> 

Thanks,

-- 
Ian Costello   Phone: +61 3 9963 1952
R&D Engineer   Mobile: +61 417 508 522
CXFS MultiOS

  reply	other threads:[~2008-03-08  4:40 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-03-08  4:00 [PATCH, RFC] - remove mounpoint UUID code Eric Sandeen
2008-03-08  4:31 ` Ian Costello
2008-03-08  4:33   ` Eric Sandeen
2008-03-08  4:40     ` Ian Costello [this message]
2008-03-08  4:59       ` Eric Sandeen
2008-03-08 11:54 ` Christoph Hellwig
2008-03-11  0:44 ` Nathan Scott
2008-03-11  1:19   ` Eric Sandeen
2008-03-11 20:09     ` nscott
2008-03-12  7:22       ` Christoph Hellwig
2008-07-08  3:09         ` [PATCH, RFC] - remove mountpoint " Eric Sandeen
2008-07-25  2:22 ` [PATCH, RFC] - remove mounpoint " Niv Sardi
2008-07-25  3:11   ` Eric Sandeen
2008-07-25  5:12     ` Niv Sardi

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=47D218CF.8090909@sgi.com \
    --to=ianc@sgi.com \
    --cc=ianc@melbourne.sgi.com \
    --cc=sandeen@sandeen.net \
    --cc=xfs@oss.sgi.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.