From: Joel Becker <Joel.Becker@oracle.com>
To: ocfs2-devel@oss.oracle.com
Subject: [Ocfs2-devel] [PATCH] ocfs2: Count more refcount records in file system fragmentation.
Date: Sat, 7 Aug 2010 11:39:34 -0700 [thread overview]
Message-ID: <20100807183934.GC3699@mail.oracle.com> (raw)
In-Reply-To: <1279778205-7428-1-git-send-email-tao.ma@oracle.com>
On Thu, Jul 22, 2010 at 01:56:45PM +0800, Tao Ma wrote:
> The refcount record calculation in ocfs2_calc_refcount_meta_credits
> is too optimistic that we can always allocate contiguous clusters
> and handle an already existed refcount rec as a whole. Actually
> because of file system fragmentation, we may have the chance to split
> a refcount record into 3 parts during the transaction. So consider
> the worst case in record calculation.
>
> Cc: stable at kernel.org
> Signed-off-by: Tao Ma <tao.ma@oracle.com>
This patch is now in the fixes branch of ocfs2.git.
Joel
--
Life's Little Instruction Book #347
"Never waste the oppourtunity to tell someone you love them."
Joel Becker
Consulting Software Developer
Oracle
E-mail: joel.becker at oracle.com
Phone: (650) 506-8127
prev parent reply other threads:[~2010-08-07 18:39 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-07-22 5:56 [Ocfs2-devel] [PATCH] ocfs2: Count more refcount records in file system fragmentation Tao Ma
2010-08-07 18:39 ` Joel Becker [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=20100807183934.GC3699@mail.oracle.com \
--to=joel.becker@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 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).