From: Mark Fasheh <mark.fasheh@oracle.com>
To: ocfs2-devel@oss.oracle.com
Subject: [Ocfs2-devel] [IMPORTANT] OCFS2 revision 946
Date: Wed May 26 20:16:04 2004 [thread overview]
Message-ID: <20040527011601.GH25513@ca-server1.us.oracle.com> (raw)
For the last couple of weeks we've been making some important format changes
for OCFS2. We're not done yet, but much of it is in a state where we feel it
can be merged back into trunk and played with. There are bugs, and there
will be more disk format changes, but at least now others can pitch in.
You will absolutely have to reformat your filesystems after picking up this
revision (946). The userspace tools aren't as ready for ocfs-tools trunk yet
though, so you'll need to pick up the new-dir-format branch of ocfs-tools
and use that to create ocfs2 file systems.
$ svn co http://oss.oracle.com/projects/ocfs-tools/src/branches/new-dir-format/ ocfs-tools
Those of you who have read the ext3 code might find some of this new stuff
familiar. This is because we've finally done away with our dirnode
structures and gone to something a little less... broken :)
--Mark
--
Mark Fasheh
Software Developer, Oracle Corp
mark.fasheh@oracle.com
next reply other threads:[~2004-05-26 20:16 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-05-26 20:16 Mark Fasheh [this message]
-- strict thread matches above, loose matches on Subject: below --
2004-05-26 22:26 [Ocfs2-devel] [IMPORTANT] OCFS2 revision 946 Ling, Xiaofeng
2004-05-27 0:50 ` Mark Fasheh
2004-05-27 1:52 Ling, Xiaofeng
2004-05-27 5:45 ` Joel Becker
2004-05-28 13:37 Zhang, Sonic
2004-05-28 13:55 ` Kurt Hackel
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=20040527011601.GH25513@ca-server1.us.oracle.com \
--to=mark.fasheh@oracle.com \
--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.