linux-fsdevel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Mark Fasheh <mark.fasheh@oracle.com>
To: Steve French <smfltc@us.ibm.com>
Cc: linux-kernel@vger.kernel.org, linux-fsdevel@vger.kernel.org
Subject: Re: [RFC] [PATCH] OCFS2
Date: Tue, 21 Jun 2005 15:03:13 -0700	[thread overview]
Message-ID: <20050621220313.GA7531@ca-server1.us.oracle.com> (raw)
In-Reply-To: <1119388469.5701.145.camel@stevef95.austin.ibm.com>

Hi Steve,
On Tue, Jun 21, 2005 at 04:14:29PM -0500, Steve French wrote:
> You list features which OCFS2 does not support yet in fs/Kconfig as:
>                - extended attributes
>                - readonly mount
>                - shared writeable mmap
>                - loopback is supported, but data written will not
>                  be cluster coherent.
>                - quotas
>                - cluster aware flock

I think you may have misread that... the latest patch at least has:
+	  Note: Features which OCFS2 does not support yet:

If you see anywhere our supported feature set is actually misstated, please
let me know so I can correct that immediately.

> The above three (notify/lease/acl) are particularly important for
> Samba.  Are those planned for an upcoming release?
Generally we want to be as useful as possible, so we've got a long list of
planned features. I'd need to look more closely at the issues involved with
supporting these in a clustered environment before giving you any more
specific of an answer :)

> What is the timestamp granularity in your inode on-disk format?  For
> Samba4 supporting at least a 100nanosecond time stamp (used for DCE and
> CIFS) is helpful due to the time rounding issues that can come up with
> the primitive 1 second timestamp.
OCFS2 supports subsecond timestamps via a u32 nsec fields on dinode, so I
think at least that should work for you.
	--Mark

--
Mark Fasheh
Senior Software Developer, Oracle
mark.fasheh@oracle.com

  reply	other threads:[~2005-06-21 22:03 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-06-21 21:14 [RFC] [PATCH] OCFS2 Steve French
2005-06-21 22:03 ` Mark Fasheh [this message]
2005-06-21 22:43   ` Steve French
2005-06-22  0:04     ` Mark Fasheh
  -- strict thread matches above, loose matches on Subject: below --
2005-05-18 22:33 Mark Fasheh
2005-05-18 23:35 ` Hans Reiser
2005-05-18 23:40 ` Adrian Bunk
2005-05-19  2:30 ` Kyle Moffett
2005-05-19  4:30   ` Mark Fasheh
2005-05-19  6:30 ` Daniel Phillips
2005-05-19  6:54   ` Mark Fasheh
2005-05-19 16:23     ` Daniel Phillips
2005-05-19 10:26   ` Jeff Garzik
2005-05-19 15:20     ` Lee Revell
2005-05-19 15:25       ` Jeff Garzik
2005-06-23 18:03 ` James Morris
2005-06-23 18:29   ` Mark Fasheh
2005-06-24  3:05   ` Paul Jackson
2005-06-24  3:29     ` Paul Jackson
2005-06-24  3:59     ` Mark Fasheh
2005-06-24  4:17       ` Paul Jackson

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=20050621220313.GA7531@ca-server1.us.oracle.com \
    --to=mark.fasheh@oracle.com \
    --cc=linux-fsdevel@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=smfltc@us.ibm.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 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).