All of lore.kernel.org
 help / color / mirror / Atom feed
From: Mark Fasheh <mark.fasheh@oracle.com>
To: ocfs2-devel@oss.oracle.com
Subject: [Ocfs2-devel] Re: Whats missing in mkfs?
Date: Tue Feb 17 17:09:37 2004	[thread overview]
Message-ID: <20040217230932.GL26331@ca-server1.us.oracle.com> (raw)
In-Reply-To: <200402172220.i1HMKv24008615@penguin.co.intel.com>

There's a couple of things:

We need to create and format the journal files. They should be 8 megs in
size, and default to just creating journals for nodes 1-4. Basically what
mkfs for an ext3 filesystem does. Also, the local alloc bitmap structures
need to be created as well (one for each node). If you look at the calls to
ocfs_journal_init (the exend_system_file call there) and ocfs_journal_create
and ocfs_create_new_local_alloc in ocfs_check_volume, you'll see what i
mean. Also, ocfs does a ton of other things in terms of initializing system
files to the filesystem on "1st mount" which really should be moved into the
format utility. Check out ocfs_create_root_dir_node for that.

Essentially, we're doing a *ton* of stuff in kernel space, which really
should be in userspace. If you're interested in tackling this, I'd be more
than happy to coordinate :)
	--Mark

On Tue, Feb 17, 2004 at 02:20:57PM -0800, Rusty Lynch wrote:
> The TODO list has an item about finishing mkfs.
> It looks like mkfs -t ocfs2 works fine.  Is there 
> something specific that is missing
> 
>     --rusty
--
Mark Fasheh
Software Developer, Oracle Corp
mark.fasheh@oracle.com

      parent reply	other threads:[~2004-02-17 17:09 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-02-17 16:21 [Ocfs2-devel] Whats missing in mkfs? Rusty Lynch
2004-02-17 16:58 ` Sunil Mushran
2004-02-17 17:09 ` Mark Fasheh [this message]

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=20040217230932.GL26331@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.