From: Mark Fasheh <mark.fasheh@oracle.com>
To: ocfs2-devel@oss.oracle.com
Subject: [Ocfs2-devel] important: ocfs2 version number bump
Date: Thu Feb 5 17:49:50 2004 [thread overview]
Message-ID: <20040205234947.GC26471@ca-server1.us.oracle.com> (raw)
*** WARNING: None of this should be attempted on a production file system.
We've bumped up the version number in the ocfs2 module. This means however
that it won't mount ocfs1 filesystems. To be able to mount with ocfs2, you
MUST download, build and install the current SVN version of ocfs-tools and
do one of the following:
1) Format as a version 2 filesystem. Run mkfs.ocfs2 with the same options as
you used to use with 'mkfs.ocfs'. For example:
mkfs.ocfs2 -b 4 -L ocfs2_test -m /ocfs2 /dev/sdb1
2) If you have an existing version 1 filesystem, then you can use the
tuneocfs '-c 2' option to bump up the version number. You will not be able
to go back to version 1 after this.
tuneocfs -c 2 /dev/sdb1
This option is currently undocumented as it is changing rapidly. Again, NONE
of this should be attempted on a production file system.
--Mark
--
Mark Fasheh
Software Developer, Oracle Corp
mark.fasheh@oracle.com
next reply other threads:[~2004-02-05 17:49 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-02-05 17:49 Mark Fasheh [this message]
-- strict thread matches above, loose matches on Subject: below --
2004-02-06 12:49 [Ocfs2-devel] important: ocfs2 version number bump Villalovos, John L
2004-02-06 14:13 ` Mark Fasheh
2004-02-06 14:27 ` Rusty Lynch
2004-02-06 14:40 ` Wim Coekaerts
2004-02-06 16:03 Villalovos, John L
2004-02-06 16:42 ` Mark Fasheh
2004-02-06 16:24 Villalovos, John L
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=20040205234947.GC26471@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.