ocfs2-devel.oss.oracle.com archive mirror
 help / color / mirror / Atom feed
From: Tao Ma <tao.ma@oracle.com>
To: ocfs2-devel@oss.oracle.com
Subject: [Ocfs2-devel] [PATCH 0/2 V2] ocfs2: Resolve the problem of truncate log flush.
Date: Sun, 19 Sep 2010 15:19:53 +0800	[thread overview]
Message-ID: <4C95B999.1080307@oracle.com> (raw)

Hi all,

change log form v1 to v2:
0001: no change.
0002 is removed and now we use jbd2_journal_start_commit in local mode 
as suggested by Joel.

     Recently, one of our colleagues meet with a problem that if we 
write/delete a 32mb files repeatly, we will get a ENOSPC in the end. And 
the corresponding bug is 1288.
http://oss.oracle.com/bugzilla/show_bug.cgi?id=1288

So this patch set just tries to resolve it. It includes 2 patches:
0001 adds a new watermark for truncate log, FLUSH_TRUNCATE_LOG_RATIO. So 
if the truncate log has collected too much clusters, 
ocfs2_truncate_log_needs_flush will tell the caller to flush immediately.

0002 try to add journal checkpoint support if we finds the need for 
checkpointing what truncate log has freed. for cluster mount, it is 
simple and we just need to wake up the ocfs2cmt and let it work for us.
For local mode, we will call jbd2_journal_start_commit directly which 
will start the checkpoint.

Regards,
Tao

             reply	other threads:[~2010-09-19  7:19 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-09-19  7:19 Tao Ma [this message]
2010-09-19  7:20 ` [Ocfs2-devel] [PATCH 1/2] ocfs2: flush truncate log in case it contains too many clusters Tao Ma
2010-10-12  0:23   ` Mark Fasheh
2010-10-12  4:55     ` Tao Ma
2010-09-19  7:20 ` [Ocfs2-devel] [PATCH 2/2] ocfs2: Start journal checkpoint if we have too many truncated clusters Tao Ma

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=4C95B999.1080307@oracle.com \
    --to=tao.ma@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).