linux-fsdevel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Peter Braam <braam@clusterfs.com>
To: linux-fsdevel@vger.kernel.org
Subject: Lustre & special file ops
Date: Mon, 17 Mar 2003 20:30:12 -0700	[thread overview]
Message-ID: <20030318033011.GS12121@peter.cfs> (raw)

Hi, 

Lustre is a cluster file system that has a client server architecture.
When a client opens a file, the server sees an open call.  This is
done so that the server can take care to handle open-unlinked files
correctly across cluster nodes.  For regular and directory files this
is fairly straightforward.

We also want to handle open-unlinked special files correctly, since
operations like fchmod and fstat on different cluster nodes issued on
file descriptors associated with open special files still require
synchronization through the server.

This requires non-standard open/close methods on the special files.
So we would like Lustre to roughly do something like:

ll_special_open(struct inode *inode, struct  file *file)
{
  1. do what init_special_inode installs
  2. do open RPC on the metadata server
} 

Is there an elegant, simple way to accomplish this? 

Thanks for any help!

- Peter -

                 reply	other threads:[~2003-03-18  3:32 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=20030318033011.GS12121@peter.cfs \
    --to=braam@clusterfs.com \
    --cc=linux-fsdevel@vger.kernel.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;
as well as URLs for NNTP newsgroup(s).