All of lore.kernel.org
 help / color / mirror / Atom feed
From: Li Zefan <lizefan@huawei.com>
To: ocfs2-devel@oss.oracle.com
Subject: [Ocfs2-devel] [PATCH] ocfs2: free allocated clusters if error occurs after ocfs2_claim_clusters
Date: Fri, 22 Nov 2013 09:33:26 +0800	[thread overview]
Message-ID: <528EB466.1030804@huawei.com> (raw)
In-Reply-To: <528E03CC.1010900@huawei.com>

On 2013/11/21 20:59, Joseph Qi wrote:
> From: Zongxun Wang <wangzongxun@huawei.com>
> 
> Even if using the same jbd2 handle, we cannot rollback a transaction.
> So once some error occurs after successfully allocating clusters, the
> allocated clusters will never be used and it means they are lost.
> For example, call ocfs2_claim_clusters successfully when expanding a
> file, but failed in ocfs2_insert_extent.
> So we need free the allocated clusters if they are not used indeed.
> 
> Cc: Joseph Qi <joseph.qi@huawei.com>
> Signed-off-by: Zongxun Wang <wangzongxun@huawei.com>

You must also sign the patch.

      reply	other threads:[~2013-11-22  1:33 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-11-21 12:59 [Ocfs2-devel] [PATCH] ocfs2: free allocated clusters if error occurs after ocfs2_claim_clusters Joseph Qi
2013-11-22  1:33 ` Li Zefan [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=528EB466.1030804@huawei.com \
    --to=lizefan@huawei.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.