All of lore.kernel.org
 help / color / mirror / Atom feed
From: Joel Becker <Joel.Becker@oracle.com>
To: ocfs2-devel@oss.oracle.com
Subject: [Ocfs2-devel] [PATCH 2/2] Ocfs2: Handle deletion of reflinked oprhan inodes correctly.
Date: Fri, 19 Mar 2010 18:28:10 -0700	[thread overview]
Message-ID: <20100320012810.GK15539@mail.oracle.com> (raw)
In-Reply-To: <1268961670-4712-2-git-send-email-tristan.ye@oracle.com>

On Fri, Mar 19, 2010 at 09:21:10AM +0800, Tristan Ye wrote:
> Current rule of orphan dir is that all inodes in the orphan dir
> have ORPHANED_FL, otherwise we treated it as an ERROR. this rule
> works well except for some rare cases of reflink operation:
> 
> http://oss.oracle.com/bugzilla/show_bug.cgi?id=1215
> 
> The problem is introduced by the essense of how reflink and our
> orphan_scan thread were working:
> 
>  * Orphan_scan scan the orphan dir into a queue first, and run
>    queue in a later time, we only hold the orphan_dir's lock
>    during scanning.
> 
>  * Reflink create a oprhaned target in orphan_dir at the first
>    step, and remove the targets and unset the flag at the third
>    step, these two steps respectively hold the orphan_dir's lock
>    themselves.
> 
> Based on above semantics, there is a possibility that a reflink
> inode can be moved out of the orphan dir and have its ORPHANED_FL
> cleared before the queue is run, which leads to a ERROR in
> ocfs2_query_wipde_inode().
> 
> This patch helps to judge if a orphan inode to be wiped off, which
> has NO ORPHANED_FL, is a legal alive reflinked target or not.
> 
> The patch also works for failed reflinked targets from a crash or
> other failures during the reflink operation, they can be wiped off
> as desired since these failed reflinked inodes always has ORPHANED_FL
> set ondisk.
> 
> Signed-off-by: Tristan Ye <tristan.ye@oracle.com>

	This patch has been added to the 'fixes' branch of ocfs2.git.

Joel

-- 

Life's Little Instruction Book #407

	"Every once in a while, take the scenic route."

Joel Becker
Principal Software Developer
Oracle
E-mail: joel.becker at oracle.com
Phone: (650) 506-8127

  parent reply	other threads:[~2010-03-20  1:28 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-03-19  1:21 [Ocfs2-devel] [PATCH 1/2] Ocfs2: Journaling i_flags and i_orphaned_slot when adding inode to orphan dir Tristan Ye
2010-03-19  1:21 ` [Ocfs2-devel] [PATCH 2/2] Ocfs2: Handle deletion of reflinked oprhan inodes correctly Tristan Ye
2010-03-19 23:50   ` Mark Fasheh
2010-03-19 23:59     ` Joel Becker
2010-03-20  2:03     ` tristan
2010-03-20  1:28   ` Joel Becker [this message]
2010-03-19 23:42 ` [Ocfs2-devel] [PATCH 1/2] Ocfs2: Journaling i_flags and i_orphaned_slot when adding inode to orphan dir Mark Fasheh
2010-03-19 23:54   ` Joel Becker
2010-03-20  1:27 ` Joel Becker
2010-03-20  1:35   ` tristan
2010-03-22  2:58   ` tristan
  -- strict thread matches above, loose matches on Subject: below --
2010-03-01  7:23 Tristan Ye
2010-03-01  7:23 ` [Ocfs2-devel] [PATCH 2/2] Ocfs2: Handle deletion of reflinked oprhan inodes correctly Tristan Ye

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=20100320012810.GK15539@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 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.