All of lore.kernel.org
 help / color / mirror / Atom feed
From: Chris Mason <chris.mason@oracle.com>
To: "Yan, Zheng" <zheng.yan@oracle.com>
Cc: linux-btrfs@vger.kernel.org
Subject: Re: [PATCH 3/4] change how subvolumes are organized
Date: Mon, 21 Sep 2009 17:01:22 -0400	[thread overview]
Message-ID: <20090921210122.GF10825@think> (raw)
In-Reply-To: <4AB37AAF.5040508@oracle.com>

On Fri, Sep 18, 2009 at 08:18:55PM +0800, Yan, Zheng wrote:
> btrfs allows subvolumes and snapshots anywhere in the directory tree.
> If we snapshot a subvolume that contains a link to other subvolume
> called subvolA, subvolA can be accessed through both the original
> subvolume and the snapshot. This is similar to creating hard link to
> directory, and has the very similar problems.
> 
> The aim of this patch is enforcing there is only one access point to
> each subvolume. Only the first directory entry (the one added when
> the subvolume/snapshot was created) is treated as valid access point.
> The first directory entry is distinguished by checking root forward
> reference. If the corresponding root forward reference is missing,
> we know the entry is not the first one.

This is a good compromise between wanting all the features and something
maintainable.  I like how it closes the directory looping and a bunch of
the related problems.

Pretty much all of the things I don't like about this approach can be
solved with a recursive snapshotting ioctl, and that can easily be added
later.

Fantastic, thank you!

-chris

      reply	other threads:[~2009-09-21 21:01 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-09-18 12:18 [PATCH 3/4] change how subvolumes are organized Yan, Zheng
2009-09-21 21:01 ` Chris Mason [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=20090921210122.GF10825@think \
    --to=chris.mason@oracle.com \
    --cc=linux-btrfs@vger.kernel.org \
    --cc=zheng.yan@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.