From: Mark Fasheh <mark.fasheh@oracle.com>
To: ocfs2-devel@oss.oracle.com
Subject: [Ocfs2-devel] [PATCH 1/3] Add online resize support for ocfs2, take 2
Date: Fri Nov 30 15:43:39 2007 [thread overview]
Message-ID: <20071130234244.GG28607@ca-server1.us.oracle.com> (raw)
In-Reply-To: <20071127081123.GA4345@tma-pc1.cn.oracle.com>
On Tue, Nov 27, 2007 at 04:11:23PM +0800, tao.ma wrote:
> Modification from V1 to V2:
> Divide the whole processes into 2 steps like ext3.
> 1) If the last group isn't full, tunefs.ocfs2 will call
> OCFS2_IOC_GROUP_EXTEND first to extend it. All the main work is
> done in kernel.
> 2) For every new groups, tunefs.ocfs2 will call OCFS2_IOC_GROUP_ADD
> to add them one by one. The new group descriptor is initialized
> in userspace, we only check it in the kernel and update the
> global_bitap, super blocks etc.
One more blanket comment about these patches - be sure to run the patched
source through the "sparse" tool. It will help us catch endian bugs when
reading/writing on-disk fields. LWN actually has a good tutorial:
http://lwn.net/Articles/205624/
--Mark
--
Mark Fasheh
Senior Software Developer, Oracle
mark.fasheh@oracle.com
prev parent reply other threads:[~2007-11-30 15:43 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-11-27 0:12 [Ocfs2-devel] [PATCH 1/3] Add online resize support for ocfs2, take 2 Tao Ma
2007-11-27 0:20 ` [Ocfs2-devel] [PATCH 1/3] Initalize bitmap_cpg of ocfs2_super to be the maximum Tao Ma
2007-11-30 11:47 ` Mark Fasheh
2007-11-27 0:22 ` [Ocfs2-devel] [PATCH 3/3] Implement "GROUP_ADD" for online resize, take 2 Tao Ma
2007-11-30 15:21 ` Mark Fasheh
2007-12-02 18:08 ` tao.ma
2007-12-03 19:24 ` Mark Fasheh
2007-12-12 23:06 ` tao.ma
2007-11-27 0:23 ` [Ocfs2-devel] [PATCH 2/3] Add group extend " Tao Ma
2007-11-27 17:34 ` tao.ma
2007-11-30 11:42 ` Mark Fasheh
2007-11-30 15:43 ` 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=20071130234244.GG28607@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.