All of lore.kernel.org
 help / color / mirror / Atom feed
From: Srinivas Eeda <srinivas.eeda@oracle.com>
To: ocfs2-devel@oss.oracle.com
Subject: [Ocfs2-devel] Suggestions to fix orphan dir cleanup
Date: Thu, 12 Feb 2009 00:27:42 -0800	[thread overview]
Message-ID: <4993DD7E.1020907@oracle.com> (raw)

Hi all,

In 1.4 and 1.2 there is a hole that leaves orphans in a orphan directory 
till fsck was run or recovery occurs on that slot.

In the current implementation, if node A did rm of a file while it is 
opened by node B. Now if node A umounts and node B dies and is restarted 
first, it only recovers itself leaving orphan file in node A's orphan 
directory.

In order to fix the problem, I am  looking for your inputs on what is 
the best :)

1) recover all slots(osb->max_slots) whenever there is a recovery. This 
can trigger simultaneous recoveries if there were multiple node failures.

2) queue recovery  during mount(even if the journal is clean). This can 
still leave the file in orphan directory till the slot is used.

3) Initiate recovery periodically after certian interval. I do not see 
much benefit in this.

thanks,
--Srini

                 reply	other threads:[~2009-02-12  8:27 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=4993DD7E.1020907@oracle.com \
    --to=srinivas.eeda@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.