Skip to content

ocfs2: Resolve the problem of truncate log flush.

Tao Ma ocfs2-devel 2 versions – New

Get series with b4
b4 am [email protected]

Versions newest first · linked by author and title

  1. v2 Latest2 patches 0 repliesNew
  2. v10 of 3 patches 0 repliesSuperseded

Patches in v2 No applies recorded yet

#Subject and filesSizeRepliesApplied
1/2ocfs2: flush truncate log in case it contains too many clusters.fs/ocfs2/alloc.c fs/ocfs2/ocfs2.h+26 -11 reply
1/2ocfs2: flush truncate log in case it contains too many clusters.+0 -00 replies
2/2ocfs2: Start journal checkpoint if we have too many truncated clusters.fs/ocfs2/alloc.c fs/ocfs2/alloc.h fs/ocfs2/journal.c +2 more+35 -100 replies

Reviews trailers per patch

No Reviewed-by, Acked-by or Tested-by trailers for v2 yet.

Read the v2 thread

Cover letter [Ocfs2-devel] [PATCH 0/2 V2] ocfs2: Resolve the problem of truncate log flush.

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