mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: "braam" <braam@clusterfs.com>
To: <arjanv@redhat.com>, <hch@infradead.org>
Cc: <torvalds@osdl.org>, <akpm@osdl.org>,
	<linux-kernel@vger.kernel.org>,
	"'Phil Schwan'" <phil@clusterfs.com>
Subject: RE: [PATCH/RFC] Lustre VFS patch
Date: Sat, 29 May 2004 00:56:40 +0800	[thread overview]
Message-ID: <20040528165649.91F1F3100D3@moraine.clusterfs.com> (raw)
In-Reply-To: <1085406284.2780.13.camel@laptop.fenrus.com>

Hi Arjan, 

> -----Original Message-----
> From: Arjan van de Ven [mailto:arjanv@redhat.com] 
> 
> fun question: how does it deal with say a rename that would 
> span mounts on the client but wouldn't on the server? :)


Mostly checks are done like in sys_rename.  

Some cases require new distributed state in the FS, such as the fact that a
certain directory is a mountpoint, possibly not on the node doing a rename,
but on another node.  

For this the Linux VFS has no api - we added something we call "pinning" for
this in 2.4, but not in 2.6 yet.

- Peter -


  parent reply	other threads:[~2004-05-28 16:57 UTC|newest]

Thread overview: 26+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-05-24 11:39 Peter J. Braam
2004-05-24 11:46 ` Jens Axboe
2004-05-25  1:48   ` braam
2004-05-25  6:47     ` Jens Axboe
2004-05-25  8:21       ` braam
2004-05-25  8:27         ` Jens Axboe
2004-05-25 10:52         ` Lars Marowsky-Bree
2004-05-25 11:45           ` braam
2004-05-25 13:35           ` Kevin Corry
2004-05-25 13:55             ` Jens Axboe
2004-05-24 12:00 ` hch
2004-05-24 12:01 ` hch
2004-05-24 12:03 ` hch
2004-05-24 15:33   ` Horst von Brand
2004-05-25 20:43     ` hch
2004-05-24 12:05 ` hch
2004-05-24 18:06   ` Trond Myklebust
2004-05-25  8:21     ` braam
2004-05-24 12:08 ` hch
2004-05-24 13:44   ` Arjan van de Ven
2004-05-24 13:53     ` viro
2004-05-28 16:56     ` braam [this message]
2004-05-28 17:00       ` Christoph Hellwig
2004-05-24 14:19 ` viro
2004-05-28 23:18 ` Maneesh Soni
2004-05-29 17:53 ` Anton Blanchard

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=20040528165649.91F1F3100D3@moraine.clusterfs.com \
    --to=braam@clusterfs.com \
    --cc=akpm@osdl.org \
    --cc=arjanv@redhat.com \
    --cc=hch@infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=phil@clusterfs.com \
    --cc=torvalds@osdl.org \
    /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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®